Facebook
Twitter-
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
-
We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.
Issue Rename a subscription not rename all
- Thread starter Azurel
- Start date
U
UFHH01
Guest
Hi Azurel,
Pls. see your OWN, UNIQUE settings at for example:
... and change the settings to your very own, desired settings! Pls. sync the plan with the domains, if you want and immidiate change after possible changes to your corresponding hosting plan.
Pls. see your OWN, UNIQUE settings at for example:
Home > Service Plans > Hosting Plans > YOUR-HOSTING-PLAN-NAME > ( tab ) Hosting Parameters
... and change the settings to your very own, desired settings! Pls. sync the plan with the domains, if you want and immidiate change after possible changes to your corresponding hosting plan.
Azurel
Silver Pleskian
I don't understand what you mean. Is this a workaround to re-create the 503 page with correct domain? I have actual no access to plesk, so I must look later.
Plesk 12.5#48
I have a subscription with domain-name "AAA.TLD". Now I rename this domain-name to "BBB.TLD" and after set a temporary suspend I see on website that this message is still for domain "AAA.TLD" which not exists anymore (was renamed to "BBB.TLD").
Plesk 12.5#48
I have a subscription with domain-name "AAA.TLD". Now I rename this domain-name to "BBB.TLD" and after set a temporary suspend I see on website that this message is still for domain "AAA.TLD" which not exists anymore (was renamed to "BBB.TLD").
U
UFHH01
Guest
Hi Azurel,
on some occasions, there might be left-over configuration files, which could be solved by using the command:
If you experience that the domain "AAA.TLD" is still reachable via your browser, then pls. check as well, that the DNS - settings at your domain registrar has been changed/modified/deleted and make sure, that the browser cache has been deleted for the domain, so that you don't see a cached site on your computer you use the browser with. If you want us to check that, you have to provide the real name for the FQDN(s).
on some occasions, there might be left-over configuration files, which could be solved by using the command:
plesk repair web -v
or
/usr/local/psa/admin/sbin/httpdmng --reconfigure-all
Pls check as well, that the domain "AAA.TLD" is not listed anymore at "/var/www/vhosts/system/", after you renamed it.or
/usr/local/psa/admin/sbin/httpdmng --reconfigure-all
If you experience that the domain "AAA.TLD" is still reachable via your browser, then pls. check as well, that the DNS - settings at your domain registrar has been changed/modified/deleted and make sure, that the browser cache has been deleted for the domain, so that you don't see a cached site on your computer you use the browser with. If you want us to check that, you have to provide the real name for the FQDN(s).
Azurel
Silver Pleskian
Hello UFHH01,
Thanks. I have tested it with
# /usr/local/psa/admin/sbin/httpdmng --reconfigure-all
that not working here.
I see in /var/www/vhosts/BBB.TLD/error_docs the html-files for errors. All this files have still in it the string "Web Server at AAA.TLD" the wrong domain name. That files was not updated with rename domain name in plesk. The filetime is older.
Hint: This was the second rename for this "domain".
Thanks. I have tested it with
# /usr/local/psa/admin/sbin/httpdmng --reconfigure-all
that not working here.
I see in /var/www/vhosts/BBB.TLD/error_docs the html-files for errors. All this files have still in it the string "Web Server at AAA.TLD" the wrong domain name. That files was not updated with rename domain name in plesk. The filetime is older.
Hint: This was the second rename for this "domain".
Last edited:
