Skip to content
This repository has been archived by the owner on Mar 17, 2024. It is now read-only.

Cannot sign in #42

Open
CattopyTheWeb opened this issue May 25, 2023 · 12 comments
Open

Cannot sign in #42

CattopyTheWeb opened this issue May 25, 2023 · 12 comments

Comments

@CattopyTheWeb
Copy link

CattopyTheWeb commented May 25, 2023

So when I enter my servers' private ip and port and all that stuff, I just get stuck loading. I enter the server ip in this format https://{private server ip}:{port}. The server doesn't have an SSL certificate, so maybe that's the issue?
Any help is appreciated.

@CattopyTheWeb
Copy link
Author

Also, I downloaded the app from F-droid

@Geezus42
Copy link

Geezus42 commented May 26, 2023

I can't either, downloaded from Play store. Last release was 7mo ago, I wonder if it's dead?

@Geezus42
Copy link

Geezus42 commented May 26, 2023

Found another.

#39

@zbejas
Copy link
Owner

zbejas commented May 27, 2023

So when I enter my servers' private ip and port and all that stuff, I just get stuck loading. I enter the server ip in this format https://{private server ip}:{port}. The server doesn't have an SSL certificate, so maybe that's the issue? Any help is appreciated.

Try http://{server}:{port} if you're not using SSL.

@CattopyTheWeb
Copy link
Author

I can't either, downloaded from Play store. Last release was 7mo ago, I wonder if it's dead?

I don't think it's dead

@CattopyTheWeb
Copy link
Author

CattopyTheWeb commented May 27, 2023

So when I enter my servers' private ip and port and all that stuff, I just get stuck loading. I enter the server ip in this format https://{private server ip}:{port}. The server doesn't have an SSL certificate, so maybe that's the issue? Any help is appreciated.

Try http://{server}:{port} if you're not using SSL.

I did try that, but it just spat out an error. Authentication failed

@CattopyTheWeb
Copy link
Author

I solved this by getting an SSL cert with nginx proxy manager and duckDNS.
Tho, I will keep this post open so we can figure out why it does that.

@CattopyTheWeb
Copy link
Author

@zbejas Maybe you should make it so it ignores SSL cert errors and just connects

@gooddavvy
Copy link

Great solution!

@bookamp
Copy link

bookamp commented Sep 11, 2023

For anyone still having this this issue, I fixed it by enabling http on the legacy 9000 port.

docker run -d -p 8000:8000 -p 9443:9443 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ee:latest --http-enabled

@lead0r
Copy link

lead0r commented Sep 11, 2023

For anyone still having this this issue, I fixed it by enabling http on the legacy 9000 port.

docker run -d -p 8000:8000 -p 9443:9443 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ee:latest --http-enabled

Thank you so much, that worked for me. I just used a different external port (9444:9000) and had to add --http-enabled

@KevinTrinh1227
Copy link

For anyone still having this this issue, I fixed it by enabling http on the legacy 9000 port.

docker run -d -p 8000:8000 -p 9443:9443 -p 9000:9000 --name=portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ee:latest --http-enabled

Thank you very much!

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

No branches or pull requests

7 participants