tom472
commented
2 years ago The new Portainer starts up with it's own self-signed cert already - nothing needs to be done in the mediabox.sh script -- that is why you see the warning when accessing it.
You can use a real cert (like Let's Encrypt) if you'd like but hat is going to take a bit of tweaking / changes that are beyond the scope of this project.
As for the Protainer link not working in Muximux - that could totally be an iframe issue or I might have a typo or something. I'll try and take a look at that ..
Sorry if this is a stupid question but I'm not an expert with certificates. I'm wondering, since this new Portainer is now using HTTPS and an IP address, will I need a self signed certificate? I already have a Let's Encrypt wildcard cert for 2 websites running on my server. 1 website is not associated with anything mediabox, but the other does point to a couple apps, reverse proxied, I allow outside users to access. Portainer is not exposed to the outside. If I use Homer to access Portainer I see that I get the standard "Potential Security Risk/Connection isn't private" warnings. And I did notice in portainer that there is some SSL Certificate section. Is it possible to have 1 CA signed cert for my websites, and a self signed cert for portainer on the 192.168 network? Think making and setting up a cert for portainer could be a function of the mediabox.sh script? Also, I'm finding that the link in Muximux doesn't work for Portainer anymore. (anything to do with loading an https page in a frame?)
Any help/info is appreciated, Bill