Selfhosted

40246 readers

858 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.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

[SOLVED] Can't access my site from WAN despite DNS and port forwarding in place. Help? [ERR_SSL_UNRECOGNIZED_NAME_ALERT] (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by PlutoniumAcid@lemmy.world to c/selfhosted@lemmy.world

10 comments fedilink hide all child comments

TLDR:

Update: the server software has a bug about generating+saving certificates. Bug has been reported; as a workaround I added the local IP to my local 'hosts' file so I can continue (but that does not solve it of course).
I suspect there's a problem with running two servers off the same IP address, each with their own DNS name?

Problem:

When I enter https://my.domain.abc into Firefox, I get an error ERR_SSL_UNRECOGNIZED_NAME_ALERT instead of seeing the site.

Context:

I have a static public IP address, and a Unifi gateway that directs the ports 80,443 to my server at 192.168.1.10 where Nginx Proxy Manager is running as a Docker container. This also gives me a _Let's Encrypt certificate.
I use Cloudflare and have a domain foo.abc pointed to my static public IP address. This domain works, and also a number of subdomains with various Docker services.
I have now set up a second server running yunohost. I can access this on my local LAN at https://192.168.1.14.
This yunohost is set up with a DynDNS xyz.nohost.me. The current certificate is self-signed.
Certain other ports that yunohost wants (22,25,587,993,5222,5269) are also routed directly to 192.168.1.14 by the gateway mentioned above.
All of the above context is OK. Yunohost diagnostics says that DNS records are correctly configured for this domain. Everything is great (except reverse DNS lookup which is only relevant for outgoing email).

Before getting a proper certificate for the yunohost server and its domain, I need to make the yunohost reachable at all, and I don't see what I am missing.

What am I missing?

you are viewing a single comment's thread
view the rest of the comments

[–] SeeJayEmm@lemmy.procrastinati.org 3 points 1 year ago

Also I would consider trying to use openssl to see what's actually happening since the browser can sometimes obfuscate things in it's attempts to be helpful.

openssl s_client -connect :443

I'm with @SheeEttin@lemmy.world in that the server should fail to start if there was no certificate to load. It's more likely that the server is providing an invalid cert. Using the openssl command above would help you identify that.