Issue Upgraded to Obsidian, blank login screen?

[Ruben]

I've just upgraded to Obisidian. The process seemed to go well, but in the end I couldn't log into Plesk.
When I go to my server address :8443, I get redirected to https://www....be:8443/login_up.php?success_redirect_url=https://www.....be:8443/ but that's an empty screen.

All I'm seeing is a blank screen that has my server address and something that looks like a missing image.

Looking at the source code of this page, I see several references to files like /cp/javascript/main.js?1576778135 etc. which supposedly run the whole thing and render the interface. All of these links give me a 404 error though.



I'm stuck here. I tried "plesk repair installation" and after some repair actions I noticed this:
Trying to start service sw-cp-server... sw-cp-serverd is stopped
Starting sw-cp-serverd: [FAILED]

When trying to start this manually I get this:

[root@server ~]# service sw-cp-server start
Starting sw-cp-serverd: nginx: [emerg] bind() to 0.0.0.0:8443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:8880 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:8443 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:8880 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:8443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:8880 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:8443 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:8880 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:8443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:8880 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:8443 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:8880 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:8443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:8880 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:8443 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:8880 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:8443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:8880 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:8443 failed (98: Address already in use)
nginx: [emerg] bind() to [::]:8880 failed (98: Address already in use)
nginx: [emerg] still could not bind()
[FAILED]

Any help is *much* appreciated here...

 

[TomBoB]

Hi try the following:
nginx fails to start due to left Apache configuration files from Kloxo panel: nginx: [emerg] bind() to 203.0.113.2:80 failed (98: Address already in use)

seems to apply to your case.
Cheers,
Tom

 

[Ruben]

Thanks Tom. I'm not sure this applies to my server though, I don't see any of the configuration files mentioned there.

I did this:
[root@server ~]# netstat -tulpn | grep 8443
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 8976/sw-cp-server
tcp 0 0 :::8443 :::* LISTEN 8976/sw-cp-server

which seems to suggest sw-cp-server is listening to 8443. It seems to contradict the fact that sw-cp-server is stopped.

 

[TomBoB]

Ahh, yes i see

try this one: Service sw-cp-server failed to start on Plesk for Linux: 98: Address already in use

Cheers

 

[Ruben]

Looks like you made my day, mate.
I had already searched myself but somehow that didn't come up. Solved the issue though, many thanks.

 

[Stanley Chauke]

Hi, I see that after the upgrade also, I cannot edit file like in the DNS

 

[Ruben]

Probably the Plesk server sw-cp-server is not running. Kill all related processes and try to start it manually via SSH and see from there.