Closed warpok closed 10 months ago
Well, oddly, https works at the site now. I don't understand why it gave the errors.
Please answer the first question.
With regard to the port number for the SSH server, the person who set up the other server may explain why he set up a port number other than the default port number 22.
On another server I use the default pot number 22 for SSH login, and that works fine.
So in other words, I don't know why a port number is needed on your other server.
Oh. It was me who set up the other server, following a pattern that I learned from Aranggi (I think). Thanks for your help!
I have two questions I hope you can help me with.
When I log into the server for the guest instance of Bibledit, I don't have to specify the port in the login string. Our other server includes the address plus -p 59594. Is it important that I set a port? If so, how do I do it? It seems the site has been working fine without one.
I have encountered a new problem. Suddenly https doesn't work. And when trying to renew certbot, I get this error message: Error: unable to resolve host. But my domain name is not up for renewal.
Actually the certbot renew command said that my certificates were still valid. So the error in the terminal probably relates to certificates. To make sure, I recopied the certificates and also gave the command to make sure they have the right file attributes. There was no change in regard to https. Why did my https break? I haven't done anything that would make any changes in the config directory.