Signed the ssl portal and deleted the ssl signature. how to log in?

Workspace
1

Ubuntu 20.04 system
Type of installation of Workspace docker Community Server

Signed the ssl portal and deleted the ssl signature.
the result is that it is not possible to log in to the portal.

how to log in?
the password is reset.
but can’t log in

2

Hello @NICOLE

If I understand correctly you are referring to HTTPS in provided description, correct me if I’m wrong.

Does it show any error when attempting to log in? Have you tried clearing browser cache before logging in again?

3

hi

The first one was without http, that is, I deployed the portal.
Then I generated an https certificate.
Then I deleted the certificate in the admin panel.

When it was first installed, I entered my username and password and everything worked, I could log in to the portal.
After generating the certificate, everything also worked and I could log in to the portal.
After the network certificate was deleted, the portal began to work over http.
And it does not allow authorization by a pair of login and password.
Despite the fact that I changed the password, it also does not allow me to enter the portal.

Еhe cache does not play a role . I used different computers and different browsers.
Restarting the portal also didn’t help.

Authorization error the login and password pair are not correct/

4

I suppose you are accessing portal via domain name, is that correct?

Did you generate certificate to enable HTTPS manually or via Control Panel > HTTPS section? Also, did you delete certificate from Control Panel too?

By the way, what was the point of disabling HTTPS after all?

Please try opening portal in Incognito mode to log in. Please make sure that you are accessing portal via HTTP in this scenario.

UPD: please share output of docker ps from machine where Workspace is installed.

6

I hit the “Delete” button on my cert because it was out of date, hoping I would see a button to get a new one, but instead I’m kicked out of the control panel now. Chrome says “This site can’t be reached – refused to connect.”

docker ps says:

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
169d30838d09 onlyoffice/controlpanel:3.5.4.541 “/var/www/onlyoffice…” 10 minutes ago Up 10 minutes 80/tcp, 443/tcp onlyoffice-control-panel
f6b61c382dab onlyoffice/documentserver:8.1.1.1 “/app/ds/run-documen…” 8 months ago Up 21 minutes 80/tcp, 443/tcp onlyoffice-document-server
86fa41abb876 onlyoffice/communityserver:12.5.2.1848 “/app/run-community-…” 14 months ago Up 21 minutes 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 3306/tcp, 5280/tcp, 9865-9866/tcp, 9871/tcp, 9882/tcp, 0.0.0.0:5222->5222/tcp, :::5222->5222/tcp, 9888/tcp onlyoffice-community-server
dc94c91470b6 onlyoffice/elasticsearch:7.16.3 “/bin/tini – /usr/l…” 14 months ago Up 21 minutes 9200/tcp, 9300/tcp onlyoffice-elasticsearch
18c67cb7971f mysql:8.0.29 “docker-entrypoint.s…” 14 months ago Up 21 minutes 3306/tcp, 33060/tcp onlyoffice-mysql-server

7

For my problem (just now realized it’s slightly different than OP’s problem) it seems the server just fixed itself, including reinstalling another SSL certificate from letsencrypt.org. I had to restart twice though, or maybe it was just about waiting long enough.

1 Like