If you cannot reach Xeams webserver, even from the local machine, there could be an issue with it. First, confirm that the webserver is running by checking the services on the local machine for Xeams. If it is running, restart the service.
Once the service has been restarted, check to see if the webserver is now reachable.
In either situation, open up Xeams.log and scroll to the very end. Slightly above the end you should see a line that looks like this:
xeams.ServerStarter - ---------------------------------------------------
This line is the restart of Xeams. If the server is now reachable you can scroll up from here and search for [ERROR] lines to see what has gone wrong.
If the server is still unreachable, search below the lines for [ERROR] lines to see what is causing the server to not start.
If you are having issues with inbound emails, check out our troubleshooting page on this here: Troubleshooting Inbound Messages
If you are having issues with outbound emails, check out our troubleshooting page on this here: Troubleshooting Outbound Messages
Certain configurations can slow down Xeams, making it unresponsive. Please take a look at the performance KB article to help you troubleshoot the root of the cause.
Additional articles/notes:
- If clustering is enabled, confirm master and slave machines are able to ping to eachother.
- If multiple-profile is enabled in Xeams, confirm you do not have too many profiles.