As a senior CMS website operation personnel in the information security industry, I am well aware of the frustration 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.start.shDisplay the situation where AnQiCMS is running but the website cannot be accessed, and we need to systematically investigate.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
Firstly, we need to confirmstart.shIs the "running" output of the script really indicating that the AnQiCMS application itself is working normally, and not just that the script itself is in a loop trying to start. Check.start.shThe log file generated by the script 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 and checkrunning.logFile.This log file records the startup process and any error information of the AnQiCMS application.If the application encounters issues during startup, such as port occupation, database connection failure, configuration errors, etc., these will be reflected in this log.check.logThe process status of AnQiCMS will be displayed. If the process starts and stops frequently, it indicates that the service itself is unstable.
If the log shows that the application starts normally without any obvious errors and the process remains running, the problem may be on the external access level.
Check the port configuration of AnQiCMS
AnQiCMS listens to the default port 8001, which is infaq.mdand multiple Docker installation tutorials are mentioned. If yourconfig.jsonThe configuration file has specified different ports, or different ports are assigned to each instance during multi-site deployment. Please ensure that AnQiCMS is actually listening on the correct port.
On Linux servers, you can uselsof -i:{端口号}commands (for examplelsof -i:8001Check if the port is occupied and listened by the AnQiCMS process. If the port is occupied by other programs, or the AnQiCMS process is not listening to any ports,start.shDisplay running, inaccessible from outside. If the port is occupied, you need to end the occupying process (kill -9 {PID}), or change the port configuration of AnQiCMS and restart.
Examine the reverse proxy configuration of web servers (Nginx/Apache)
AnQiCMS is typically deployed behind a web server (such as Nginx or Apache) and forwards external requests to the internal ports that AnQiCMS is listening on. The document ininstall.md/start.mdThis configuration is explained in detail in the installation tutorial related to Docker.
For Nginx, please check your site configuration file to ensureproxy_passThe instruction points to the correct AnQiCMS internal address and port (for examplehttp://127.0.0.1:8001).try_filesInstructions are also very important, they ensure that static files are processed first, and then forward unmatched requests to AnQiCMS. Any configuration error, such asproxy_passthe address is written incorrectly,locationThe block match rule is incorrect, or if the Nginx service itself is not started or the configuration is not reloaded, it will result in the website being inaccessible.
For Apache, although the configuration examples provided in the documentation are limited, the principle is similar. You need to ensure that the Apache reverse proxy module is enabled, andProxyPassandProxyPassReverseThe request was correctly forwarded 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 configuration are correct, external access may still be blocked at the network level.
Firstly, confirm that your domain name is correctly resolved to the server's IP address. You can useping your-domain.comor use an online DNS query tool to verify. If the domain resolution is incorrect, users will naturally be unable to access your website.
Next, the firewall of the server (such as on Linux)ufworfirewalld）or cloud service provider's security group configuration is a common obstacle.Please check these firewall rules to ensure that they allow incoming HTTP (80) and HTTPS (443) traffic to reach your web server.If your AnQiCMS instance directly exposes the port (not recommended), you need to ensure that the AnQiCMS listening port (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 it cannot provide external services.
Based oninstall.mdWith Docker deployment document, AnQiCMS usually uses MySQL.Please check if the MySQL service is running.running.logwill record error information related to 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 database required by AnQiCMS.
Multi-site deployment and special considerations for Docker environments
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 of the container (usually 8001) is correctly mapped to some port on the host.Then, the reverse proxy of the web server (Nginx/Apache) should point to this mapping port of the host instead of the internal IP and port of the container.docker-1panel.mdanddocker-bt.mdThese port mappings and reverse proxy configurations are described in detail in the documents.
For multi-site deployment,faq.mdeach AnQiCMS instance needs to occupy a different port.install.mdAlso 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 for each site points to the correct AnQiCMS instance port, and that the data and configuration between instances (especiallyconfig.jsonofportThere is no conflict.
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 cache reasons.Try clearing your browser cache or accessing the website in private mode (incognito mode).
Finally, there is a "Website Status" option in the "Global Settings" of AnQiCMS backend (}]}help-setting-system.md). If the site is set to "closed site status", then even if everything is normal, users will only see the closed site prompt information. Please log in to the backend to confirm whether the site status is open.
Through these detailed troubleshooting steps, you should be able to locate and resolve the issue of the AnQiCMS website being inaccessible.
Common Questions and Answers (FAQ)
1. Whystart.shShow AnQiCMS running, but IpingThe domain name 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 unreachable, the first thing you should check is whether 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.其次，confirm your server network connection is normal, and it is not blocked by a firewall (including the firewall on the server itself and the security group of the cloud service provider) from ICMP protocol (the protocol used by ping) or HTTP/HTTPS port.
2. I have configured Nginx reverse proxy according to the tutorial, and also restarted Nginx, but the website is still inaccessible, what should I do?
In this case, you should first check the Nginx error logs (usually located/var/log/nginx/error.logEnglishNginx error logs record any issues encountered during the proxy process, such as inability to connect to the upstream server (AnQiCMS process), permission issues, etc.proxy_passThe internal address and port specified by the directive AnQiCMS (for examplehttp://127.0.0.1:8001）and the port that AnQiCMS is actually listening on is consistent, and this port is accessible within the server, and it is not occupied by other applications or blocked by internal firewall policies.
3. AnQiCMS backend is normal, but the front-end website loads slowly or some content is missing, how to troubleshoot?
If the backend management interface can be accessed normally, it indicates that the core services and database connection of AnQiCMS are usually normal.The slow loading or loss of content on the front end is often related to template files, static resource loading, or image processing.running.logIs there an error in template parsing or file reading.Next, open the developer tools (F12) in the browser and view the Console (console) and Network (network) tabs.Console may display JavaScript errors or prompts for failed resource loading, and Network can show which files take too long to load or return error status codes (such as 404).help-source-attachment.mdMentioned that when the front-end does not update after the image upload, the local browser cache needs to be cleared, which reminds us to also pay attention to the browser cache and static resource path issues.Ensure that the paths of the static resources (CSS, JS, images) referenced in the template are correct, and that these files exist on the server.In addition, settings related to image compression and WebP format in the "Content Settings" backend may also affect the front-end loading effect if configured incorrectly.