If `start.sh` shows that AnQiCMS is running but the website is inaccessible, how should I troubleshoot?

As an experienced security CMS website operations person, I know the anxiety and unease when the system appears to be running but the website is inaccessible.This usually means there is a gap between backend services and frontend access. Facingstart.shDisplay AnQiCMS is running but the website is inaccessible, we need to investigate systematically.This is not just a check of the service itself, but also requires a review of the server environment, network configuration, and the core settings of AnQiCMS.

Confirm the actual running status of AnQiCMS service

First, we need to confirmstart.shIs the "running" output from the script really indicating that the AnQiCMS application itself is working normally, rather than just the script itself trying to start in a loop? Viewstart.shThe script-generated log file is the first step. According to the provided document,start.shThe script usually writes the output torunning.logandcheck.log.

You should enter the AnQiCMS installation directory to check,running.logFile. This log file records the startup process and any error information of the AnQiCMS application.If the application encounters problems during startup, such as port occupation, database connection failure, configuration errors, etc., these will be reflected in this log. At the same time,check.logIt will display the survival status of the AnQiCMS process, if the process starts and stops frequently, it means that the service itself is unstable.

If the log shows that the application started normally, without any obvious errors, and the process remains running, then the problem may lie in the external access level.

Check the AnQiCMS port configuration

AnQiCMS listens to the default port 8001, this isfaq.mdand are mentioned in multiple Docker installation tutorials. If yourconfig.jsonThe port is configured differently in the file, or when deploying across multiple sites, each instance is assigned a different port, please ensure that AnQiCMS is actually listening on the correct port.

On a Linux server, you can uselsof -i:{端口号}commands (for examplelsof -i:8001) Check if the port is occupied and monitored by the AnQiCMS process. If the port is occupied by other programs, or if the AnQiCMS process is not monitoring any ports, then evenstart.shThe application is running, it is also inaccessible from the outside. If the port is occupied, you need to end the occupying process (kill -9 {PID}), or change the AnQiCMS port configuration and restart.

Examine the reverse proxy configuration of the web server (Nginx/Apache)

AnQiCMS is typically deployed behind a web server (such as Nginx or Apache), forwarding external requests to the internal port that AnQiCMS is listening on. The document states thatinstall.md/start.mdand the installation tutorial related to Docker explains this configuration in detail.

For Nginx, please check your site configuration file to ensure.proxy_passThe command points to the correct AnQiCMS internal address and port (for examplehttps://en.anqicms.com)try_filesInstructions are also crucial, they ensure that static files are processed first, and then the unmatched requests are forwarded to AnQiCMS. Any configuration error, such asproxy_passaddress is written incorrectly,locationThe block matching rule is incorrect, or if the Nginx service itself is not started or the configuration has not been reloaded, the website will not be accessible.

For Apache, although the configuration examples provided in the documentation are few, the principles are similar. You need to make sure that the Apache reverse proxy module is enabled andProxyPassandProxyPassReverseThe command correctly forwarded the request to the listening port of AnQiCMS.

After modifying the Web server configuration, be sure to reload or restart your Web server (for examplesystemctl reload nginxorsystemctl restart apache2) to make the changes take effect.

Verify domain name resolution and server firewall settings

Even if the AnQiCMS application and Web server configurations are correct, external access may still be blocked at the network level.

First, make sure that your domain name is correctly resolved to the server's IP address. You can useping your-domain.comOr verify it with an online DNS query tool. If the domain resolution is incorrect, users will naturally be unable to access your website.

Secondly, the firewall of the server (such as on LinuxufworfirewalldOr, the security group configuration of cloud service providers is a common obstacle.Please check these firewall rules to ensure that they allow incoming HTTP (80) and HTTPS (443) traffic to your web server.If your AnQiCMS instance is directly exposed to the port (not recommended), you need to make sure that the port AnQiCMS is listening to (such as 8001) is also open.

Check the database connection and status

AnQiCMS is a content management system that requires a database to store all content and configurations.If the database service is not running or AnQiCMS cannot connect to the database, the application may start but cannot provide services to the outside.

Based oninstall.mdAnd the Docker deployment document, AnQiCMS usually uses MySQL.Please check if the MySQL service is running. You can also view AnQiCMS'srunning.logwhere it records related error information of the database connection. Ensureconfig.jsonThe database credentials (host, port, username, password) provided during installation are correct, and the database user has sufficient permissions to access the AnQiCMS required database.

Special considerations for multi-site deployment and Docker environment

If you are running AnQiCMS in a Docker environment or have deployed multiple AnQiCMS instances, the troubleshooting steps will have some additional details.

In Docker, you need to ensure that the AnQiCMS container itself is running (docker ps), and the internal port (usually 8001) of the container is correctly mapped to some port on the host.Then, the reverse proxy of the Web server (Nginx/Apache) should point to this mapped port on the host machine, not the container's internal IP and port.docker-1panel.mdanddocker-bt.mdetc. documents describe these port mappings and reverse proxy configurations in detail.

For multi-site deployment,faq.mdeach AnQiCMS instance needs to occupy a different port.install.mdIt also describes how to install multiple sites on the Baota panel and configure each site to use an independent root directory, database, and Nginx reverse proxy. Make sure that the Nginx configuration of each site points to the correct AnQiCMS instance port, and that the data and configuration between different instances (especiallyconfig.jsonofportNo conflicts.

Client cache and other potential issues

Sometimes, even if the server-side issue has been resolved, your browser may still display the old error page due to caching reasons.Try clearing your browser cache or access the website in private mode (incognito mode).

Finally, there is a "Website Status" option in the "Global Settings" of the AnQiCMS backend (help-setting-system.md). If the website is set to a "closed site" status, then even if everything is normal, the user will only see the closed site prompt information. Please log in to the background to confirm whether the website status is open.

By following these detailed troubleshooting steps, you should be able to locate and resolve the issue of AnQiCMS website not being accessible.

Frequently Asked Questions (FAQ)

1. Whystart.shDisplaying AnQiCMS running, but IpingThe domain is not accessible?

start.shThe script is only responsible for starting the AnQiCMS application process and cannot solve domain resolution or network connectivity issues. If youpingThe domain is not accessible, first check if the domain has been correctly resolved to your server IP address.This is usually configured through your domain registrar or DNS service provider's control panel.Next, confirm that your server's network connection is normal and that it is not blocked by a firewall (including the firewall on the server itself and the security group of the cloud service provider) from the ICMP protocol (the protocol used by ping) or the HTTP/HTTPS port.

2. I have configured Nginx reverse proxy according to the tutorial, and also restarted Nginx, but the website still cannot be accessed, what should I do?

In this case, you should first check the Nginx error log (usually located in/var/log/nginx/error.log）。Nginx error logs record any issues encountered during the proxy process, such as inability to connect to upstream servers (AnQiCMS process), permission issues, etc.At the same time, confirm that the Nginx configuration file containsproxy_passThe internal address and port specified by the command (for examplehttps://en.anqicms.com) Consistent with the actual port that AnQiCMS is listening on, and the port is accessible within the server, not occupied by other applications or blocked by internal firewall policies.

3. How to troubleshoot if the AnQiCMS backend is normal but the front-end website loads slowly or shows missing content?

If the background management interface can be accessed normally, it indicates that the AnQiCMS core services and database connection are usually normal.The front-end loading is slow or the content is missing, which is often related to template files, static resource loading, or image processing.First, check AnQiCMS'srunning.logAre there any errors related to template parsing or file reading. Next, open the developer tools (F12) in the browser and view the Console (console) and Network (network) tabs.The console may display JavaScript errors or prompts for failed resource loading, in the Network you can see which files take too long to load or return error status codes (such as 404). Documentationhelp-source-attachment.mdMentioned that when the front-end is not updated after the image is uploaded, it is necessary to clear the local browser cache, which reminds us to also pay attention to the browser cache and static resource path issues.Ensure that the paths to the static resources (CSS, JS, images) referenced in the template are correct, and that these files exist on the server.In addition, the settings in the background "Content Settings" regarding image compression and WebP format may also affect the front-end loading effect if configured incorrectly.