Messages

1

Tutorials and FAQs / Re: Tutorial 2024/06: HAProxy + Let's Encrypt Wildcard Certificates + 100% A+ Rating

« on: July 18, 2024, 12:10:18 pm »

I'm still trying to make it work and don't understand why it's not working as expected. But, just now, as I was trying to understand why there are no HTTP code from the server showing in Firefox dev tool, so I tried with Chromium and it works 
If I look at OPNsense firewall live logs, when trying to access serviceX.local.DOMAINNAME.com, with Firefox it goes to IP:443, but with Chromium it goes to IP:5006 (the correct service port) 

It's not working either with Librewolf, Mullvad browser that are also Firefox based (this also excludes a FF profile issue).
The error:

Code: [Select]

Unable to connect

An error occurred during a connection to serviceX.local.DOMAINNAME.com.

    The site could be temporarily unavailable or too busy. Try again in a few moments.
    If you are unable to load any pages, check your computer’s network connection.
    If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the web.So I guess it's not the correct topic anymore, but if anyone as a clue of what is happening...

2

Tutorials and FAQs / Re: Tutorial 2024/06: HAProxy + Let's Encrypt Wildcard Certificates + 100% A+ Rating

« on: July 09, 2024, 05:44:38 pm »

Hello,
It's been more than a year that my setup is working (for nextcloud, accessible from "outside"), thank you TheHellSite  but now I'm adding to my network a CoreOS VM to run containers (local access only, each one with its own port number) and I want to be able to type serviceX.local.
For now, I'm going simple and will use my already set domain name: serviceX.local.DOMAIN.com
I've made the changes and it seems to work except that the "real server" port (5006) is not used (443 instead). If I type: serviceX.local.DOMAIN.com:5006 it works, but the purpose is to not have to remember all the port and that serviceX direct to the correct port number.
I've tried so many things without success that I don't remember 
Do you have an idea of what can be incorrect? (maybe HAProxy can't do that? Maybe it's the CoreOS VM that must redirect based on the domain/subdomain used?)

And second thing: how can I set a .local domain name? (with container port) I thought of Unbound DNS Overrides but it does work with port.
Like:
- service1.local redirect to 192.168.60.21:5006
- service2.local redirect to 192.168.60.21:3000
etc.

Maybe .local is not a good idea: https://en.wikipedia.org/wiki/.local

3

Tutorials and FAQs / Re: Tutorial 2023/04: HAProxy + Let's Encrypt Wildcard Certificates + 100% A+ Rating

« on: May 20, 2023, 02:47:10 pm »

Thanks for this tutorial TheHellSite.
The only difficulty I had was a mistake that I made: I set `Verify SSL Certificate: true` on the real server (nextcloud). Then I "couldn't connect" to my server (I remember I could with IP but not domain name, and on internal network not from outside) and waste several hours to spot what was wrong...