Unable to access after update

[theRealBassist]

Describe the bug
Following updating my stack, I am unable to access speedtest tracker. Previously I was able to. Now I am not.

To Reproduce
Steps to reproduce the behavior:

1. Stop my container
2. Pull the latest image
3. Start the container
4. See error

Expected behavior
When I go to the IP:PORT of the container, I should access the instance

Environment (please complete the following information):

• OS: Linux Mint
• Architecture: amd64
• Browser: Firefox
• Version: 0.11.0

Screenshots

Logs
Unknown which are applicable

Additional context
I have port 80 forwarded to 8110. However, I have also tried it with 443 and it does not work there either. I setup my container through Portainer using docker-compose. I will include a copy of it below

docker-compose.txt

[garanda21]

You have to share your container log, otherwise is imposible to know the causes!

Check this for reference: https://docs.docker.com/engine/reference/commandline/logs/

[theRealBassist]

Apologies! They will be attached below.
Logs.txt

[alexjustesen]

I wonder if this is similar to the issue in #332...

[theRealBassist]

@alexjustesen So that was actually one of the issues that I looked through before I posted here myself. The major difference that I saw was that, from what I could tell he seems to be displayed an error code from within speedtest tracker whereas mine is just flat out not connecting.

I might be misunderstanding the other issue, of course, but I can definitely see them being at least somewhat related issues.

[alexjustesen]

Have you tried the insecure port and mapping to :80?

[garanda21]

Maybe try ssl_mode ?

This issue help me in the past:

#280 (comment)

[theRealBassist]

@alexjustesen

I just tried mapping 8110:80, but to no avail.

EDIT: I just re-read your comment and I also tried mapping 80:80 as I assume that's what you meant by 'the insecure port'. Regardless, it did not seem to resolve the issue.

@garanda21

I tried setting SSL_MODE=off (in conjunction with mapping 8110:80) in the environment section of my docker-compose, but also to no avail.

[alexjustesen]

Yeah ssl mode is now "mixed" by default so you have the flexibility to map to either 80 or 443 so I don't think it's that.

Can you attach your logs?

[alexjustesen]

@theRealBassist v0.11.1 was just released that removes the trusted proxy restrictions. This should improve ease of use when working with different proxy services. If you continue to have issues please post in this discussion.

#364