• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Issue All domains redirect to /login_up.php after automatic update

simonedev

New Pleskian
Good evening everybody.
I have a local server in my office, and a static IP connection.

This is my configuration:
- Ubuntu 22.04.5 LTS
- Plesk 18.0.69 Update 4 (auto updated)

This morning I discovered that all the sites hosted on my server redirect to https://domain-name/login_up.php
In add, even if I enter my plesk username and password, I cannot login.

I'm still able to login from https://my-ip:8443

I tried to restart all services and I checked all ports to prevent odd conflicts between Nginx and Apache. All seems fine, because both services starts with no errors.

Somebody told me to reinstall Nginx and Apache from "plesk installer". Maybe it's a solution, but I want to be sure about the risks. I remember I spent hours to make the email server (Postfix / Dovecot) work properly.

Thanks in advice for any suggestion.
 
Hello, @simonedev . Have you tried the Plesk repair utility already? If not, could you please try running the following command:

plesk repair web -y

In case the issue persists afterward, could you please provide us with the contents of /var/www/vhosts/system/example.com/conf/vhost.conf for an example domain name that experiences the reported issue?
 
Hello, @simonedev . Have you tried the Plesk repair utility already? If not, could you please try running the following command:



In case the issue persists afterward, could you please provide us with the contents of /var/www/vhosts/system/example.com/conf/vhost.conf for an example domain name that experiences the reported issue?
I rud that command a couple of times. No errors reported but nothing changed with my problem.

Here you find the content of
/var/www/vhosts/system/example.com/conf/http.conf (I have no vhost.conf inside that folder)

I want to add that, after reading some suggestions on the web, I set Apache to respond on ports 7080 and 7443 to not conflict with 80 and 443 managed by Nginx. i don't know if it was a silly mistake, since until yesterday everything was working fine.
 

Attachments

  • httpd.conf.zip
    1.6 KB · Views: 1
Can you please temporarily switch that to "No custom URLs: Only https://<server-IP-or-hostname>:8443" and let us know if the issue still persists?
 
I just did it, and restarted the server too.
Unfortunately nothing changed for me.
 

Attachments

  • Screenshot 2025-06-12 171219.png
    Screenshot 2025-06-12 171219.png
    35 KB · Views: 1
Back
Top