Skip to main content

ea-nginx reverse proxy and clearing cache on triggered reload

Comments

1 comment

  • cPRex Jurassic Moderator

    Hey there!  After you updated the conf.json file, did you run this command?

    /scripts/ea-nginx conf --all

    That would save the changes and reload the service.

    However, I'm not sure any service will let you use cache after the service has been reloaded, which will happen frequently on a cPanel server.  Picture a MySQL database, for example - if you have cached tables, and stop the service, that table cache gets cleared - nginx is no different.  Any action in cPanel or WHM that changes user data and triggers an Apache/nginx restart will reload the server and dump the cache.

    Since that's the case, configuring the time to be 128 days is completely possible, but other mechanisms will likely clear that cache sooner.

    0

Please sign in to leave a comment.