Was fixed but now appears again!!😱

Question

Closed this issue 5 months ago · 3 comments

          Was fixed but now appears again!!😱

Originally posted by @DonPablo1010 in #82 (comment)

Answer 1 · 2024-07-12T20:04:54.000Z

Now it works again and the error message is gone... Don't see anything related in the container logs...🤷🏼‍♂️

Answer 2 · 2024-07-13T06:31:09.000Z

It's probably the a nameserver in you're near that didn't updated yet it can be take up to 24h :/

Answer 3 · 2024-07-13T06:31:22.000Z

But it's fixed:)