• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

HTTP restart required for new subdomains?

I

IMspintheweb

Guest
Hi

I was wondering if anybody else is running into this since upgrading to plesk 7.5.4

Used to be able to access newly created subdomains right after creation, but now we have to restart the apache daemon after every new subdomain, is kinda annoying
 
7.5.4 restart

Yes. We are running 4 PSA 7.5.4 servers and we have the same problems on all of them.

We thought it was our security causing it, but we re-imaged one server and found the same thing to be true without adding any firewall rules or apps.
 
Re: 1and1

Originally posted by phatPhrog
You guys aren't using 1and1.com by any chance?

Yes, do ya think is it a 1 and 1 issue, not plesk?
 
Inclination

I'm inclined to believe so. Am working on it.

Are you using the 1n1 firewall, the plesk firewall or your own server based firewall?

1n1 has just made some major changes to their Cisco based firewall so you may look at that. I did and it has solved the problem on one of our servers - (for now)

We'll see.
 
mhm 1and1 told me its a plesk issue, because it executes a wrong command.

the issue does involve apache restarting in some other cases..

- password protected directories
- domain/subdomain creating

has anybody fixed that? or do i really need to create a cronjob every hour?
 
Back
Top