Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Portainer error: Client sent an HTTP request to an HTTPS server. #37

Closed
notDavid opened this issue Dec 23, 2022 · 3 comments · Fixed by #40
Closed

Portainer error: Client sent an HTTP request to an HTTPS server. #37

notDavid opened this issue Dec 23, 2022 · 3 comments · Fixed by #40

Comments

@notDavid
Copy link

Hi again,

so opening https://portainer.mydomain.nl/ gives me this error in my webbrowser: Client sent an HTTP request to an HTTPS server.

Changing the port from 9443 to 9000 in the config fixes it.

Is it a bug or config error on my side?

Thank you!

PS.
I haven't figured out how to set the password yet, whatever i set PORTAINER_ADMIN_PASSWORD to i always get Unauthorized 🤷🏼‍♂️

@notDavid
Copy link
Author

Okay, i figured out how to set the admin password (source)

So let's say the password is test1234:

$ htpasswd -nbB admin 'test1234'
admin:$2y$05$QbX5CFLupABLCSv51ks6D.RA/pQoIvxmqdqfd.W21Uh0TC7sRx26y
  1. You now have to escape each $ with another $, like so:
`$$2y$$05$$QbX5CFLupABLCSv51ks6D.RA/pQoIvxmqdqfd.W21Uh0TC7sRx26y`
  1. Set this as PORTAINER_ADMIN_PASSWORD in .env

@maximelafarie
Copy link

@notDavid I confirm you it's not a bug, I also had to change the port to 9000

Thank you for your feedback, it helped me a lot. It definitely should be mentioned in the docs or as comment in the .env file.

Again, many thanks 🙏

@jfroment
Copy link
Owner

Sorry for the late fix, indeed some changes in Portainer were breaking, and as I do not use Portainer anymore, I did not encounter the issue myself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants