NethServer Version: NS8-alpha Module: cluster-admin I have a brand-new installation of NS8 under Rocky 9.1 in a public VPS. It has a public IP address, public DNS records, and is accessible to the world on port 80. Rocky itself is completely stock; the only package I’ve installed manually is na…

[image] dan: How does NS8 determine what its FQDN is, and how can it be changed? It doesn’t: most containers inherit the system configuration. Since different distributions have different tools, NS8 leaves the network and FQDN to the admin. I didn’t test a machine named localhost, but I’ve …

…and I’m not sure if it’s related, but the system seems to think its FQDN is localhost.localdomain. When I created the cluster, I set its FQDN (to the one above), and that’s also the system hostname. Is there some other place I need to tell the system its FQDN?

The problem should be this one: 2023-03-08T07:22:26-05:00 traefik1 time="2023-03-08T12:22:26Z" level=error msg="Unable to obtain ACME certificate for domains \"ns8.familybrown.org\" : cannot get ACME client acme: error: 400 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-acct :: urn:ietf:p…

[image] giacomo: contact email \"root@localhost.localdomain\" Interesting, but kind of consistent with what I’d seen elsewhere. When I installed Prometheus, it formed a URL of http://localhost.localdomain/blahblahblah . [image] giacomo: How did you changed the machine name? hostnamect…

How does NS8 determine what its FQDN is, and how can it be changed? I don’t see that there’s a setting in the cluster-admin dashboard to do it.

[image] giacomo: So verify that the systems really sees your hostname. Well, that’s interesting. hostname returns the expected result, but hostname -f returns localhost.localdomain–which is likely where the problem’s coming from. An edit to /etc/hosts seems to have resolved the problem, at …

I had exactly the same problem with my first NS8 test installation from two days ago. When installing the base system (Debian 11) I gave the maschine the name: “servername.local”. After that, I installed NS8 and created the cluster with the first node (leader). Then i installed the samba AD with a…

I’ve added a card for this issue: Trello

NethServer Community

TLS Certificate fails in NS8

Bug

alpha, ns8

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled