Closed justinclift closed 6 years ago
This is just a reminder note to myself. At present, the DB4S service on dbhub.io is still using the old db4s-beta.dbhub.io server.crt file.
So, even though the server starts up and listens on port 5550, DB4S itself barfs when presented with this mismatching server certificate.
It just needs a new one generated and put on the server, with the dbhub-db4s service then restarted.
Closing, as this was done a while ago.
This is just a reminder note to myself. At present, the DB4S service on dbhub.io is still using the old db4s-beta.dbhub.io server.crt file.
So, even though the server starts up and listens on port 5550, DB4S itself barfs when presented with this mismatching server certificate.
It just needs a new one generated and put on the server, with the dbhub-db4s service then restarted.