cannot connect portainer with https
-
- OMV 5.x
- majh0
-
-
Does your swag log show you're getting a cert? Your port forwarding does not look right to me
-
-
I'm not sure how, as his port forwarding is not right. I suspect if he shows us his swag log, he is not getting a cert.
-
thank you for giving me a hand
macom KM0201 swag is running fine and is getting the certs. Check the links i posted.
I made a access token below pictures but it gives me same error..
-
I'm not sure how, as his port forwarding is not right. I suspect if he shows us his swag log, he is not getting a cert.
This is his portainer running ok: https://portainer.majh.duckdns.org/#!/auth
I assume he is running OMV on other ports, so forwaring 80 -> 80 and 443 -> 443 will work.
-
I'm not sure how, as his port forwarding is not right. I suspect if he shows us his swag log, he is not getting a cert.
I can show you log but how can I show you..?
-
majh0 You set up swag correctly. I can access your OMV and portainer UI and it has a valid cert.
Are you in the lan so you can try restarting the container using direct access?
If not, try to re-install portainer from the OMV UI., you will not loose the settings.
The problem may not at all be related to the proxy.
-
Are you in the lan so you can try restarting the container using direct access?
I can connect to omv ui via lan so I restarted it
then after connecting to https://portainer.majh.duckdns.org/, it gave me a same error when I restarted the swag container.. xD
-
I think Portainer UI is different from omv ui and other typical website.. this might be the reason I guess..
bcs I can do anything on omv ui with https://admin.majh.duckdns.org/ xD
come to think of it.. I think I am bothering you guys too much...
you guys are really kind and sincere..
I think I have to study more to solve this problem...
this time is not the proper one to make it for me xD
anyways thank you so much for your assistance..
although I couldn't solve this problem, I am really surprised and impressed that strangers gave me hands alot
-
Check, if websockets are passed through. That is my last guess.
-
The IP to use is the LAN IP, NOT the docker IP
-
172.30.1.40 is the host ip. not very common, but true
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!