When managing the AnQiCMS site, you may need to adjust the reverse proxy configuration of Apache or Nginx according to your needs.These configuration modifications, whether for changing the domain name, port mapping, SSL certificate settings, or optimizing performance rules, require specific operations to take effect on the web server.The configuration file saved and exited does not immediately make your site operational. The web server needs to be informed of these changes and reload the configuration.

[en] Operation after Nginx reverse proxy configuration

[en] If you are using Nginx as the reverse proxy server for AnQiCMS, after modifying the configuration file (usually located/etc/nginx/sites-available/or/etc/nginx/conf.d/In the directory, as well as/etc/nginx/nginx.confAfter the main configuration file is saved and exited, you need to perform the following steps to apply the changes and ensure the service runs normally.

Firstly, it is strongly recommended that you check the syntax of the configuration file before reloading the Nginx service.This step can help you find potential syntax errors and avoid the service from failing to start due to incorrect configuration.

sudo nginx -t

If the output showssyntax is okandtest is successfulThe configuration file syntax is correct. If an error occurs, you need to go back to the configuration file according to the prompt information and make corrections.

After confirming that the configuration file is correct, you can safely reload the Nginx service using the following command. The reload (reload) operation applies the new configuration smoothly without interrupting the current requests being processed:

sudo systemctl reload nginx

Or, if your system does not usesystemdManage service, you can use:

sudo service nginx reload

Or send a signal directly through the Nginx binary file:

sudo nginx -s reload

Operations after Apache reverse proxy configuration

For users using Apache as the reverse proxy server for AnQiCMS, after modifying the Apache configuration file (such ashttpd.conf/apache2.confor located insites-availableAfter the virtual host configuration file in the directory is opened and "save and exit" is clicked, measures must also be taken to make the configuration effective.

Like Nginx, you should first verify that the Apache configuration file syntax is correct. This helps prevent Apache services from failing to start due to incorrect configuration:

sudo apachectl configtest

or

sudo httpd -t

If returnedSyntax OKit means the configuration is correct. If there is an error, please modify the configuration file according to the prompts.

After confirming that the configuration file is correct, you can reload the Apache service to apply the changes. UsegracefulOption reloading is a recommended approach because it allows Apache to restart its process without interrupting existing connections:.

sudo apachectl graceful

Or, if your system usessystemd:

sudo systemctl reload apache2 # (适用于Debian/Ubuntu等系统)

or

sudo systemctl reload httpd # (适用于CentOS/RHEL等系统)

The check and restart of AnQiCMS application process

Under normal circumstances, modifying the reverse proxy configuration and reloading the web server is sufficient to ensure normal access to the AnQiCMS site.Because of the modification at the reverse proxy level, it will not directly affect the operation process of AnQiCMS.AnQiCMS as an independent Go language application usually runs on a specific port (such as 8001) and provides services to the outside world via a reverse proxy.

However, in some extreme cases, such as long-term configuration errors of the web server causing AnQiCMS connection timeout, or server resource tension causing AnQiCMS process abnormal termination, you may need to check the running status of AnQiCMS itself.

To check if the AnQiCMS process is still running, you can use the following command:

ps -ef | grep anqicms

This command will list all processes containing the string "anqicms". If you see something similar./anqicmsoranqicmsProcess information, and if the process is the AnQiCMS application you started, it means it is running.

If the AnQiCMS process is not running or you suspect it is running abnormally, you can try to restart it. In the AnQiCMS deployment directory (for example/www/wwwroot/anqicms.com/），usually there will be onestart.shThe script is used to start AnQiCMS. Firstly, you may need to terminate any existing AnQiCMS processes: Findps -ef | grep anqicmsThe PID of processes related to AnQiCMS in the command output (usually the number in the second column). Then execute:

kill -9 <PID> # (将<PID>替换为实际的进程ID)

Navigate to the installation directory of AnQiCMS after the cleanup is complete, and execute the startup script:

cd /path/to/your/anqicms/installation # (替换为您的实际路径)
./start.sh

If AnQiCMS is running assystemda service configuration, you can use:

sudo systemctl restart anqicms

Verify site access

After completing the above operation, open your browser and enter the domain name of the AnQiCMS site to access.

If everything is configured correctly, you should be able to access the site pages normally. If you still encounter problems, please check the error logs of the web server (Nginx's)error.logor Apache'serror_log) as well as the log files of the AnQiCMS application itself (usuallyrunning.logorcheck.log), which will provide valuable troubleshooting clues.

Common Questions (FAQ)

Q1: Why do I need to reload rather than simply restart the web server after modifying the reverse proxy configuration?

A1:Reload (reloadorgracefulAn is a more smooth service update method.It allows the web server to continue processing existing client requests while loading new configurations.This means that your website will not experience service interruption during configuration updates.restartThis will immediately terminate all existing connections and restart the service, which will cause a brief service interruption. It is recommended to use a smooth reload in production environments.

Q2: If the AnQiCMS site still cannot be accessed after I execute the above command, what should I do for troubleshooting?

A2:If the site is still inaccessible, you can investigate from the following aspects:

  • Check the web server logs: View the Nginx'serror.logor Apache'serror_logFile, look for any error or warning messages. This usually points to issues in the reverse proxy configuration or with AnQi