Search results

  1. thekendog

    1.6.9 Issue

    I think I found the issue actually. I am using monit and was getting the PID from /tmp/lshttpd/lshttpd.pid. For whatever reason this was causing problems. Instead of monitoring the process I'm gonna check a host now. Seems to be working properly now.
  2. thekendog

    1.6.9 Issue

    Just updated to 1.6.9 from 1.5.8. I can't restart OLS now. I'm seeing this error. Refusing to accept PID outside of service control group, acquired through unsafe symlink chain: /tmp/lshttpd/lshttpd.pid I'm on Centos 7.
  3. thekendog

    Updated to OLS 1.6.7, Password Protected Directory with Realm and Context Not Working Now

    That worked. Not sure what changed in 1.6.7 but obviously something did.
  4. thekendog

    Updated to OLS 1.6.7, Password Protected Directory with Realm and Context Not Working Now

    I did not. I resorted to using the Wordpress password protection feature. It seems to be a bug in the latest version.
  5. thekendog

    Configure PHP by Directory or File Error Using Rewrite Method

    Yeah I ended up doing that. This worked for me. RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{THE_REQUEST} \s/([^?.]+)(?:\.php)?[?\s] [NC] RewriteRule ^ - [H=application/x-httpd-lsphp73]
  6. thekendog

    Updated to OLS 1.6.7, Password Protected Directory with Realm and Context Not Working Now

    Doesn't work. I am still getting the prompt to login but the username and password doesn't work.
  7. thekendog

    Updated to OLS 1.6.7, Password Protected Directory with Realm and Context Not Working Now

    What does it need to be? Currently it's 644 with lsadm as the owner and group.
  8. thekendog

    Updated to OLS 1.6.7, Password Protected Directory with Realm and Context Not Working Now

    I'm getting a prompt for login, it's just that the defined user and password in the realm file isn't working.
  9. thekendog

    Updated to OLS 1.6.7, Password Protected Directory with Realm and Context Not Working Now

    It's in a vhost template and the info says this... Syntax: It can be an absolute path or path relative to $SERVER_ROOT, $VH_ROOT, or $DOC_ROOT. $DOC_ROOT is the default relative path, and can be omitted. So I assumed I can leave that blank as $DOC_ROOT is the default value.
  10. thekendog

    Updated to OLS 1.6.7, Password Protected Directory with Realm and Context Not Working Now

    realm authorized_users { userDB { location $SERVER_ROOT/conf/vhosts/mydomain.com/authorized_users } } context /my_page/ { allowBrowse 0 realm authorized_users rewrite { } addDefaultCharset off phpIniOverride...
  11. thekendog

    Configure PHP by Directory or File Error Using Rewrite Method

    I've followed the guide here... https://openlitespeed.org/kb/setup-per-directory-file-php/ ...and am using the alternate rewrite method. However, all images, css files, js files, etc are throwing either a 500 error or this... Resource interpreted as Stylesheet but transferred with MIME type...
  12. thekendog

    lsphp74-zip on CentOS 7

    When will the zip module for php 7.4 be added for CentOS 7? I've got a plugin on a Wordpress site that needs it to function.
  13. thekendog

    Context in a VHost Template

    That's what I figured. Was just hoping there way a way around having to go that route. Thanks for the help.
  14. thekendog

    Context in a VHost Template

    I have a VHost template and a context rule I'd like to add. I've added it and it works, however I get notifications in the error log because it's trying to apply it to all sites in the template. Is it possible to specify a specific vhost when applying a context rule in a template?
Top