After setting up the environment, I try to use thunderbolt as client. It detects the correct configuration for an address with enforced TLS incoming/outgoing, but then it asks me to add an exception to hostname:port, and it won’t because it can’t acquire the certification. After checking with openssl command, I found out that it won’t print anything, unless I replace the hostname with server ip. It doesn’t make sense.
Considering the server has a nginx installed inside the host along with the containerized one (I guess it has nothing to do with), everything but this works.
I don’t know what’s left to fully link the hostname to public ip. I also tried to add a line inside etc/hosts file, but… nothing.
So, how to fix this?

  • ppal replied to this.

    • ppal

    • Best Answerset by ppal

    ppal I realized I put a wrong value for PTR record (would be better if docs provided an example of that, like any other dns settings), so I don’t need to add a hostname, especially if it already has a FQDN. Then I deleted the ssl folder and restarted the host machine.

      • Pppal

          Moolevel 0
        • Post #2
        • Edited
        • Best Answerset by ppal

        ppal I realized I put a wrong value for PTR record

        docs.mailcow.email
        https://docs.mailcow.email/prerequisite/prerequisite-dns/#reverse-dns-of-your-ip-address
        No preview could be generated for this link
        (would be better if docs provided an example of that, like any other dns settings), so I don’t need to add a hostname, especially if it already has a FQDN. Then I deleted the ssl folder and restarted the host machine.

          Have something to say?

          Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

          Just wondering whether you are your own ISP or if your ISP delegated a larger public IP range to you, including reverse DNS zone? If yes, you don’t need an example in the docs, because then you probably know how to manage your reverse zone.

          If the above does not apply to you, then the reverse DNS zone is manged by your ISP or your hosting provider, which means you can’t setup a PTR record yourself, but your ISP / hosting provider has to do it for you.

          And of course the hostname of your server must appear in the PTR record. A PTR record basically does the same thing as the A record, but it does it the other way around. It points from the IP to a domain name or to a FQDN. Here’s an example:

          1.2.3.4.in-addr.arpa. IN PTR mail.example.com.

          No one is typing