Unable to access the web interface

[DOMGO-cut]

Regularly can't access the web interface, and no errors were found after troubleshooting the logs. smtp and api work fine. Restarting the service didn't help, only reinstalling it brought it back to normal, but after a few hours it was inaccessible again.

[willpower232]

Are you using caddy or something to provide access to the web UI? What are you seeing in your browser when it does not work?

I presume your postal status shows everything is working?

[nickgupta33]

I am facing a similar issue. Caddy, server, worker, smtp all working in postal status. Shows 404 when I try to hit the webui after installation.

[Som23Git]

Hey @nickgupta33,

Assuming, you must be using the latest version of the postal i.e. v3.

Caddy, server, worker, smtp all working in postal status

That's perfect.

Shows 404

What is the URL you are trying to hit?

If you are using default config, you have Caddy pointing to 127.0.0.1:5000 to access the webUI. Are you using a domain name or are you trying to access the instance using the external & ephemeral IP address? Where is this postal instance is configured?

[Som23Git]

Hi @DOMGO-cut

Regularly can't access the web interface, and no errors were found after troubleshooting the logs. smtp and api work fine. Restarting the service didn't help, only reinstalling it brought it back to normal, but after a few hours it was inaccessible again.

When facing issues with the web interface, there are typically two possibilities:

1. Ephemeral IP Address: If your instance is using a dynamic IP (e.g., if it's a spot instance), the IP address might change over time. This would require updating the A records to reflect the new IPv4 or IPv6 addresses. You might have already noticed these changes happening. Assuming, you have persistent tasks and disk to run.

2. Static IP and DNS Issues: If your instance is using a static IP with fixed resources, the issue could be DNS-related. Your domain may be inaccessible from certain networks due to DNS resolution problems. For example, you may be able to access the web UI from one network using router A, but it’s inaccessible from another network using router B, potentially due to /etc/resolv.conf or /etc/hosts settings.

You can use tools like MxToolBox to check if the nameservers and A records are accessible when the web UI becomes unavailable. If it's not responding with the expected results then, you have your solution.

Suggestion: Kindly provide more details like screenshots, ERROR or DEBUG logs when starting a discussion so we can assist you more effectively.

P.S.: I’m not affiliated with MxToolBox, just recommending a useful tool that could help you troubleshoot this issue.