bind9 fails

[pedroponte]

I get an error message when starting the container:

Starting domain name service...: bind9 failed! Any idea how I can troubleshoot this?

TIA

[jhmaverick]

Hi Pedro, did this error happen in the first time you ran the container? Have you tried running a DNS rebuild for all users? Maybe that solves.

You can try something like this:

for f in /home/*; do \
    v-rebuild-dns-domains "$(basename -- "$f")"; \
done

[pedroponte]

Hi João, thank you.  I deleted the data folder and re-run the container, thank you, nice work 👌

---

From: João Henrique @.***> Sent: Monday, November 21, 2022 15:35 To: jhmaverick/hestiacp-docker Cc: pedroponte; Author Subject: Re: [jhmaverick/hestiacp-docker] bind9 fails (Issue #5)

Hi Pedro, did this error happen in the first time you ran the container? Have you tried running a DNS rebuild for all users? Maybe that solves. You can try something like this:

for f in /home/*; do \ v-rebuild-dns-domains "$(basename -- "$f")"; \ done

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>

[pedroponte]

Update. Actually, after trying to access today, I see this error: nginx: [emerg] bind() to xx-xx-xx-xx:80 failed (99: Cannot assign requested address) Nginx server is down, any clues? TIA On 2022-11-21 16:35, Pedro Ponte @.> wrote: > > > Hi João, thank you. > > I deleted the data folder and re-run the container, thank you, nice work 👌 > > > > From: João Henrique @.> > Sent: Monday, November 21, 2022 15:35 > To: jhmaverick/hestiacp-docker > Cc: pedroponte; Author > Subject: Re: [jhmaverick/hestiacp-docker] bind9 fails (Issue #5) > > > > > Hi Pedro, did this error happen in the first time you ran the container? > Have you tried running a DNS rebuild for all users? Maybe that solves. > You can try something like this: > > > for f in /home/*; do \ v-rebuild-dns-domains "$(basename -- "$f")"; \ done > > > — > Reply to this email directly, view it on GitHub (https://github.com/jhmaverick/hestiacp-docker/issues/5#issuecomment-1322246023), or unsubscribe (https://github.com/notifications/unsubscribe-auth/ABKBI7QDZKJ5AITUF7RQMELWJOJDZANCNFSM6AAAAAASE7JRMY). > You are receiving this because you authored the thread.Message ID: @.***>

[pedroponte]

I have updated the container to privileged mode and now it works. Would you think this is the best approach? TIA On 2022-11-21 20:32, Pedro Ponte @.> wrote: > > Update. > > > > Actually, after trying to access today, I see this error: > > > > > > nginx: [emerg] bind() to xx-xx-xx-xx:80 failed (99: Cannot assign requested address) > > > > Nginx server is down, any clues? > > > > TIA > > > > > > > On 2022-11-21 16:35, Pedro Ponte @.> wrote: > > > > > > > > Hi João, thank you. > > > > I deleted the data folder and re-run the container, thank you, nice work 👌 > > > > > > > > From: João Henrique @.> > > Sent: Monday, November 21, 2022 15:35 > > To: jhmaverick/hestiacp-docker > > Cc: pedroponte; Author > > Subject: Re: [jhmaverick/hestiacp-docker] bind9 fails (Issue #5) > > > > > > > > > > Hi Pedro, did this error happen in the first time you ran the container? > > Have you tried running a DNS rebuild for all users? Maybe that solves. > > You can try something like this: > > > > > > for f in /home/; do \ v-rebuild-dns-domains "$(basename -- "$f")"; \ done > > > > > > — > > Reply to this email directly, view it on GitHub (https://github.com/jhmaverick/hestiacp-docker/issues/5#issuecomment-1322246023), or unsubscribe (https://github.com/notifications/unsubscribe-auth/ABKBI7QDZKJ5AITUF7RQMELWJOJDZANCNFSM6AAAAAASE7JRMY). > > You are receiving this because you authored the thread.Message ID: **@.***>