Self-Hosted Main

515 readers

1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

Service: Dropbox - Alternative: Nextcloud
Service: Google Reader - Alternative: Tiny Tiny RSS
Service: Blogger - Alternative: WordPress

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

Awesome-Selfhosted List of Software
Awesome-Sysadmin List of Software

founded 1 year ago

MODERATORS

[email protected]

Can't use my own SSL certificate for Portainer? (alien.top)

submitted 1 year ago by [email protected] to c/[email protected]

1 comments fedilink hide all child comments

I set up the Nginx proxy manager container to avoid the "not secure" warnings on my internal Docker containers. They all seem to work with my duck.dns SSL certificates and I can access them using custom domain names (e.g. Plex.duck.dns.org) but when I try it with Portainer, I get this error on Chrome. Firefox and other browsers don't show the error but tell me that my connection is still not secure. Does anyone here know why and how I could fix it?

https://preview.redd.it/7rsxc10mh60c1.png?width=897&format=png&auto=webp&s=d0532cef522c6b7fb2c482c8d946b9a0bb7fd6a0

top 1 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 1 year ago

This is unlikely to be a portainer issue and more a config issue with that server in npm. Bit hard for us to troubleshoot without seeing the real error behind this. What does a browser like edge tell you? What does this one say say if you click details?