• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Resolved 502 bad gateway login page

solucionesuno

solucionesuno

Regular Pleskian
after inset the creadencials in login page i get this screen

i update this server from 12.5 to 17.5 a few days ago
 

Attachments

  • download.png
    download.png
    87.4 KB · Views: 4
It happen sometimes just after update from 12 to 17.
I think it come from configuration not completly reloaded.
So restart psa is the solution ! ;)

Cheers.
 
You must log in or register to reply here.

Similar threads

Daveo
Issue Debian 13: Apache Issues
Replies
13
Views
4K
mow
M
X
Issue Cloudflare DNS Extension Fails with JsonException when Cloudflare returns non-JSON errors (502/524)
Replies
1
Views
860
Sebahat.hadzhi
Sebahat.hadzhi
Z
Resolved Plesk updates failing: 502 Bad Gateway after installer update + “Unable to receive update information” error
Replies
1
Views
1K
zihniates
Z
J
Issue Control Panel URL redirects to https://localhost:8443/smb/
Replies
9
Views
2K
WebHostingAce
WebHostingAce
H
Resolved Laravel app "502 Bad Gateway" on page reload only
Replies
2
Views
3K
halnex
H
Back
Top