This info also assumes you have successfully installed APC Cache on your server, and set up a clean install of Virtualmin with Nginx as the Alternative Web Server.
Accordingly, the suggested configuration is for WordPress installed in a subfolder.
I prefer to install WordPress in public_html/wordpress for ease of development, compatibility with other scripts, etc.
I deploy many WordPress sites with W3 Total Cache and APC Alternative PHP Cache, so I was very interested to see how Nginx performance compares to Apache for WordPress, and whether APC and W3TC would play nice with Nginx. Virtualmin now includes support for Nginx web server. You might see a few repeated entries, especially if your pages always contain the same image.By Chris Gilligan on Main Web Server Performance Tuning, Wordpress Once the login button is selected and the correct credentials are used, then the response that is returned back to the browser should come with HTTP headers that contain Set-Cookie to indicate a user is logged in so that the next time a page from the same site is loaded in the same browser, a cookie is sent to the server to indicate the user has already logged in before.Īnd if you want to increase the chances of server requests being logged from you, just turn off caching for a while and do your testing. The most important header to look for is: Set-Cookie If you want to go more technical, then look for HTTP headers on each request using an advanced command line tool like CURL or maybe may help as well, especially with page timings. This results in every user seeing the same content as a guest would. There's also a possibility that cookie values were not used at the time the page is requested after successful login. To workaround this problem temporarily, configure your web browser to disable all forms of caching and turn on cookies. When you login and press the login button, if the load time is ridiculously fast compared to the first time the login screen has loaded, then you know that the previous page was cached and then being reloaded. It sounds like your web browser is naturally caching the problematic login pages and/or the headers returned for the login pages are not correct.Ĭheck the speed of the page load. Proxy_set_header Host $host:$server_port My system auth log isn't getting pinged by the login attempts, so webmin isn't even making the login call via PEM (it's getting stopped before that).ĭoes anybody know what could explain this 401 error in my log, or more generally, what might be keeping webmin login from working? Note the 401 (not authorized) error status.īefore I set up the reverse proxy, successful logins looked like this:ġ45.23.98.124 - "GET /admin/config/session_login.cgi HTTP/1.1" 401 2840ġ45.23.98.124 - root "POST /session_login.cgi HTTP/1.1" 200 871 The login page has all assets (images, js, etc.) properly loaded. When I go to /webmin, the login page shows up as you'd expect- but when I try to login, the login page simply reloads (no error message, no success). I've created a reverse proxy for webmin through nginx to run webmin at /webmin instead of port 10000 (:10000).
0 kommentar(er)
