Self singed SSL problem after upgrade

[GogoFC]

Question

Hello

Using docker compose with a self signed cert.

After I upgrade from V 2.0.3 to any newer version I can't connect to Dashy in Browser.

On version 2.0.3 logs I get HTTPS server successfully started (port: 443 of container) , I don't see that message after upgrading.

Volumes are all OK I checked the location of certs inside container at /etc/ssl/certs/ they're there.

If the certs weren't there I think there would be error SSL Not Enabled: Public key not present1 , I don't get that error so I guess it read the certs.

I checked for ports running inside container and I don't see port 443 anymore.

tcp        0      0 127.0.0.11:37203        0.0.0.0:*               LISTEN      -
tcp        0      0 :::80                   :::*                    LISTEN      63/node

What could I look into.

[liss-bot]

Welcome to Dashy 👋
It's great to have you here, but unfortunately your ticket has been closed to prevent spam. Before reopening this issue, please ensure the following criteria are met.

Issues are sometimes closed when users:

• Have only recently joined GitHub
• Have not yet stared this repository
• Have not previously interacted with the repo

Before you reopen this issue, please also ensure that:

• You have checked that a similar issue does not already exist
• You have checked the documentation for an existing solution
• You have completed the relevant sections in the Issue template

Once you have verified the above standards are met, you may reopen this issue. Sorry for any inconvenience caused, I'm just a bot, and sometimes make mistakes 🤖

[GogoFC]

bad bot

[Lissy93]

Hiya @GogoFC
Sorry about that, it's helpful to know that it was 2.0.4 onwards that it stopped working, as that must have been caused by #528

All the SSL stuff happens in /services/ssl-server.js, which wasn't modified, so the only thing I can think could of caused it would be this line 🤔

[jsabanal]

Hi, sorry I encounter the same issue. What should be a work around? Thanks

[liss-bot]

This issue has gone 6 weeks without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days.

[GogoFC]

2.1.0 fixed it. Thanks.