Sometimes, when accessing the VoipNow interface and the Call Reports area in particular, an error stating "504 Gateway timeout" might occur. This means that the web server (Nginx) could not get a response from the backend (PHP script).
This might occur because of the following reasons:
- the high number of call records in MySQL and the extended processing they require;
- a possible PHP error; you can find out more about this in /usr/local/voipnow/admin/log/php_error.log;
- a possible server issue (low CPU, memory, IO, etc).
There is no perfect solution for this because it requires extensive debugging. However, you can use the workaround described below:
Make a backup of /usr/local/httpsa/etc/httpsa-admin.conf using the following command:
cp /usr/local/httpsa/etc/httpsa-admin.conf /usr/local/httpsa/etc/httpsa-admin.conf.bk
Edit /usr/local/httpsa/etc/httpsa-admin.conf and add the following lines in the http section before INCLUDE. This will increase specific read/send timeouts to 120 seconds.
Restart the httpsa service using the following command:
service httpsa restart
If the issue persists, it is recommended to contact the Professional Services team.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 4.0 International.