Search results

  1. G

    503 error + [lsphp]: Failed to listen socket [/tmp/lshttpd/lsphp.sock]: No space left on device

    @Cold-Egg: Here is what I have in mind: 1) If /tmp is full because of the session files left by lsphp, then it would seem OLS should clean them up on a regular basis. 2) Maybe it's obvious to experienced users that it's the /tmp that's full. The message could be a little more explicit. Most...
  2. G

    503 error + [lsphp]: Failed to listen socket [/tmp/lshttpd/lsphp.sock]: No space left on device

    It would be great if the error message could be tweaked to be a little more meaningful. @lky, could you explain why the phpsessionclean service/timer are not enough to do the cleaning job? @Cold-Egg, is there a reason this is not part of OLS setup if it is necessary? @margin707, you will run...
  3. G

    What is the best way to make changes without creating database / disk corruptions?

    I have come to the conclusion that I am not doing things quite right to avoid database / disk errors, when either restarting OLS, restarting lsphp processes, installing server updates... I think one of the things that trip me up are WP cron jobs that keep running from crontab files every so many...
  4. G

    "No request delivery notification has been received from LSAPI application, possible dead lock."

    Looking at my server logs, I have not experienced the "No request delivery notification" message since 11/14. I unfortunately do not know what I changed at that point that may have made a difference. My shell history does not go that far back. I don't see any server restart between the 12th and...
  5. G

    OpenLiteSpeed with mod_security running as reverse proxy (WAF)

    Is the nginx server running on the same machine or a different machine? I see the proxy address is defined as: address 172.16.0.188:80 but it looks like your listener is also on port 80. I would also advise again calling the proxy extapp and the virtual host both 'nginx'. That's sure to create...
  6. G

    In passthrough https traffic, OpenLiteSpeed option "useIpInProxyHeader 1" does not work

    You may want to look at 'Use Client IP in Header' on the Server Configuration > General tab. This may help: https://help.cachewall.com/article/71-real-client-ips-litespeed
  7. G

    Quic / http/3 not working in version 1.7.1 directadmin version

    It came back after I stopped lsws, killed all lsphp processes, and restarted lsws. Will probably go away again at some point. At least that has been my experience. Works after restart only for a while.
  8. G

    Quic / http/3 not working in version 1.7.1 directadmin version

    Well, what do you know, today http/3 is gone again. One thing I did was enabling high debug server log and then turning it off. Another one was adding this to the headers: and this to the .htaccess file: # Pick webp images when available <IfModule mod_rewrite.c> RewriteEngine on RewriteCond...
  9. G

    Quic / http/3 not working in version 1.7.1 directadmin version

    Update: Running lsup.sh -e 1.7.7 today to get the updated development release (for a separate caching issue) seems to have re-enabled http/3 & QUIC.
  10. G

    How to always have a short server TTFB?

    Thank you, this helps. How does this parameter interact with 'Connection Keep-Alive Timeout'? What's the default setting for 'Connection Keep-Alive Timeout' and what's a good setting for it? I think Cyberpanel sets it to 1 second. Is this setting moot in http/2 and http/3?
  11. G

    WP admin bar disappearing as if public cache page is being served

    This just started happening again soon after I disabled Cloudflare proxying to try to see if HTTP/3 & QUIC were working with OLS 1.7.7 (which they are not). David (who replied to my bug report email thread) says it's a usage issue, not a server bug. I don't really understand how this could a...
  12. G

    Quic / http/3 not working in version 1.7.1 directadmin version

    Okay, will do. PS: If I was still using CF, I think the 'server' header would say Cloudflare instead of LiteSpeed.
  13. G

    Quic / http/3 not working in version 1.7.1 directadmin version

    I disabled the plugin for now and cleared the cache. No change as far as I can see but the cf-edge-cache header is now gone.
  14. G

    Quic / http/3 not working in version 1.7.1 directadmin version

    Is that a problem? This is added by the Cloudflare Wordpress plugin: // add header unconditionally so we can detect plugin is activated if (!is_user_logged_in() ) { header( 'cf-edge-cache: cache,platform=wordpress' ); } else { header( 'cf-edge-cache: no-cache'...
  15. G

    Quic / http/3 not working in version 1.7.1 directadmin version

    Okay, Cloudflare disabled, here is my url: https://swinginatthesavoy.com/ Just tested with Chrome and https://http3check.net/?host=swinginatthesavoy.com, no luck. My server and vhost QUIC settings are attached.
  16. G

    Quic / http/3 not working in version 1.7.1 directadmin version

    Nevermind, totally forgot I had re-activated Cloudflare for now because I could not get http/3 to work reliably anyway. So in my case, Cloudflare is now the problem. Apologies for the mislead. Let me disable it and rerun.
  17. G

    How to always have a short server TTFB?

    My understanding is that the difference is at least partly due to not having lsphp already running for the first one. Is there a way to keep it running? PS: I need a bit more time to generate traces for the other websites that use caching.
  18. G

    How to always have a short server TTFB?

    Here is a site that does not use any sort of caching. One request shows 1.12 sec of waiting time, the other one 186 ms.
  19. G

    How to always have a short server TTFB?

    When I run my sites through GTMetrix, I sometimes see a short server TTFB and other times it's much longer, several seconds. I do not understand why this is the case. It's as if there was some really long server startup time. This usually happens when no accesses have been done for a bit. Any...
  20. G

    OpenLiteSpeed with mod_security running as reverse proxy (WAF)

    @edan, it might be more efficient for you to share your /usr/local/lsws/conf/httpd_config.conf and /usr/local/lsws/conf/vhosts/proxy-vhost/vhost.conf files here or with LiteSpeed tech support.
Top