Search results

  1. Cold-Egg

    Problem with wordpress installation

    Hi, Please share the comment you ran and the error output here so we can help.
  2. Cold-Egg

    Install Composer Globally

    It means PHP is not found, you might need to install it first. To install lsphp, please follow https://docs.litespeedtech.com/lsws/extapp/php/getting_started/, or https://docs.openlitespeed.org/installation/script to install OLS, PHP, MariaDB at one time.
  3. Cold-Egg

    Installation won't upgrade on Ubuntu

    The package hasn't been ready to push to the LiteSpeed repo yet, it will be fixed in the next few days.
  4. Cold-Egg

    Install Composer Globally

    Not sure if I get your point, but if you install it under the document root folder, then your app should be able to run it, right? Get composer with the script, see https://getcomposer.org/doc/faqs/how-to-install-composer-programmatically.md, and it seems no cli is required.
  5. Cold-Egg

    Error install php

    Just a reminder, you may encounter other new issues since some old necessary dependency packages are not easy to install on the Alamalinux 8.
  6. Cold-Egg

    Wildcard Include in httpd_config

    While restarting the web server, did you notice anything unusual? any error? If none, please raise a ticket with us support@litespeedtech.com with this forum post link appended, so we can help you check further from there.
  7. Cold-Egg

    Wildcard Include in httpd_config

    It works from my test, may I know if there's any invalid conf under that custom folder?
  8. Cold-Egg

    Error install php

    Curious, which OS are you using?
  9. Cold-Egg

    azure openlitespeed-wordpress image removed

    No problem, please consider using or migrating the new image version in the future.
  10. Cold-Egg

    How to Add Custom Conf File

    I guess you might need to userewrite rules and apply them to each virtual hosts. https://store.litespeedtech.com/store/index.php?rp=/knowledgebase/90/Replace-SetEnvIf-with-RewriteRule-to-block-bad-clients.html For the insert part, you can consider the virtual host template or use the include...
  11. Cold-Egg

    upgrade OpenLiteSpeed 1.7.19 to 1.8.0 Failed to start litespeed!

    The fixed package hasn't push yet, please wait for a few days and try it again.
  12. Cold-Egg

    Need help with implementing Authorization with Realms on certain URL

    Hi Pete, Protect the CyberPanel should be good enough since you access the phpmyadmin via the Cyberpanel. Here are the steps: 1. Remove the CyberPanel port, follow https://community.cyberpanel.net/t/how-to-remove-port-8090-from-cyberpanel/30648 2. Create realm protection, follow...
  13. Cold-Egg

    azure openlitespeed-wordpress image removed

    @azlitesp Just published, please confirm if it works.
  14. Cold-Egg

    azure openlitespeed-wordpress image removed

    Ubuntu 9? Anyway, I have forwarded your request and hope we can restore the old image in the next few days.
  15. Cold-Egg

    How to Add Custom Conf File

    Could you share some example rules?
  16. Cold-Egg

    OPen lite speed server is not opening on new Installation

    No need to delete it, probably a firewall somewhere that you need to allow port 7080. It could be on the network level or system level. Form my point of view, no difference to the web server.
  17. Cold-Egg

    How to update PHP on virtual hosts?

    Glad to know it works now.
  18. Cold-Egg

    My openlitespeed virtual host external app does not run as required user

    OpenLiteSpeed process runs as nobody(in nogroup group) user, so we usually set 750 to the document root folder and owned by the [virtual host user]:[nogroup], so the web server has permission to access it.
  19. Cold-Egg

    stuck process downloading ols1clk on ubuntu 22.04?

    Is it a WSL system? To fix that error message, you can try following this post, https://superuser.com/questions/1539972/wget-error-bash-windows-subsystem-for-linux
  20. Cold-Egg

    OPen lite speed server is not opening on new Installation

    If you can curl it via localhost or 127.0.0.1 from the same server, then it means a firewall issue somewhere.
Top