Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


112 Topics 752 Posts
  • LAMP - Package Updates

    1 Votes
    35 Posts


    Enable apache alias module
  • How to host a website on LAMP?

    0 Votes
    14 Posts

    @timconsidine said in How to host a website on LAMP?:

    So Noodl does not require the MondoDB connection ?

    Noodl is primarily a frontend builder.

    It's just that it has first-class connectors for Parse (which is based on MongoDB), to add the data layer for your app.

    Anyway, you can bring any data source (accessible via REST/GRAPHQL/Static) to your app in Noodl.

  • Server utility paths

    0 Votes
    5 Posts

    Ah, thanks, good to know.

  • Node.js in LAMP server?

    2 Votes
    9 Posts

    @micmc Nice idea, maybe @girish can make it easily configurable with the FileManager (like PHP version) where LAMP/MERN/MEAN is selectable or any combination in between!

    That would be unique and slick!

  • Redirect domain root to "/site" subfolder

    0 Votes
    3 Posts
    14 Views has other ideas as well. If you want /site to appear in the browser URL, you can also do RewriteRule ^$ /site [L] (no trailing slash!)

  • Try install OpnForm

    1 Votes
    15 Posts

    Thank you so much all, for your suggestion, it solved my problem also.

  • Disable Strict Mode Mysql

    Moved Solved
    0 Votes
    18 Posts

    @girish Thanks for your prompt reply. Ok I will try to contact them to inquire about this. Will keep you guys updated. Best wishes !

  • 1 Votes
    5 Posts

    Noted. thank you for your responsiveness @girish

  • 1 Votes
    7 Posts

    @robi this is interesting! I will have a look

  • git error into public directory

    1 Votes
    3 Posts

    Thank you.

    Did solve my issue.


  • Unable to access file publicly

    0 Votes
    5 Posts

    @girish said in Unable to access file publicly:

    @shrey said in Unable to access file publicly:

    PHP Fatal error: Uncaught Error: Class "Tqdev\PhpCrudApi\Config" not found in

    The above is the error. There is no such class.

    Indeed, there's some issue in the code of the api.php itself, which is the main cause.


  • nginx.conf

    1 Votes
    12 Posts

    No one in the universe understands how an nginx.conf file works in a LAMP environment - because it doesn't! The syntax in an nginx.conf file is very different from a LAMP - Apache.conf file. One will not work in the other. So, either you are working in a LEMP stack without realizing it, or it isn't an nginx.conf file. gives some clues, perhaps, of what you are trying to do. Two things I saw in that list that I'm not sure are part of a Cloudron LAMP install is the nodejs config.json file/location, and the ffmpeg item. I don't think either come with the LAMP installation; but this isn't a Cloudron problem per se. No LAMP offering automatically comes with those two items pre-installed and functioning (but the way those two are shown in the image is confusing because it looks like they are IN the root directory of the web server???)

    It's important to understand that all the talk about Cloudron being so simple and easy is due to the context of Docker. If what you are trying to do has been using Docker, or requires Docker... then Cloudron is the absolute easiest and most powerful option available. If you are managing your web server on it's own server, by hand, then you are able to install whatever, wherever, and make the connections however (although there are typically strict conventions for most software), then Cloudron really isn't necessary. I in fact have a separate VPS on which I just run 3 LAMP php-based apps because there were complications and incompatibilities doing so in a Docker-based LAMP environment. The PHP app you are trying to install clearly assumes a non-Docker, native LAMP environment.

    On a second reading of the instructions in that link above, I actually suspect you probably followed ALL the steps in the instructions, but you ARE in a LAMP environment, and when you got to the NGINX.CONF section you still followed the instructions... except the webserver isn't using nginx, it is using Apache - so even though you placed the nginx.conf script correctly ("it works"), it isn't being used. And nginx also isn't even running, otherwise you'd get an error message that Apache can't start up because another app is using the required ports.

    So we are back at @robi's statement - "how is anyone on the forum supposed to know what you are trying to do in the OP?" Next time, include things like the various links I added. And be clearer. I hope you see by this point how unclear your request is! Look over the instructions again, then look carefully at the Cloudron LAMP folder structure - tell us in which folder you put what, for example.

    Two last things: this PHP app requires a calendar extension which I don't think the Cloudron LAMP app has (; and finally, the fact it requires PHP 5.5+ suggests it won't even work on the Cloudron LAMP app because that uses, at a minimum, PHP 7.4. And whatever runs on on pre-7.x typically doesn't run on post-7.x. Good luck!

  • 1 Votes
    5 Posts

    great, it works! thanks

  • Allow custom ports

    0 Votes
    19 Posts

    @robi said in Allow custom ports:

    Separate from the ability to manually reconfigure apache after the default install?

    The container exposes a port, 80 in this case. This 80 is hardcoded as httpPort in the manifest.

    Thinking more, maybe what you mean is: disable apache altogether, I will run something else on port 80. If this is the case, you are right that manifest does not need to be changed.

    I don't think we will support this though. It's not a normal flow to install LAMP and then disable apache as first step and run something else. This works for your specific situation only because you don't want a database or expose another port. What if I want postgres? Java? At this point, you will install everything into a data directory and run it from there. This is really not in the spirit of Cloudron.

  • Slow extraction in LAMP application

    0 Votes
    8 Posts

    I am back after a small test.

    @timconsidine Yes it is a large number of small files.

    After checking with different formats. Only started to work as it should with ".tar" format. It works like lightning with a new folder or in the current folder where the application is located.
    With this format, the extraction takes in a second and is ready.

    And I use a server from Hetzner - CX41 (Intel, 160GB Disk and 16GB RAM).


    I would still add that I had resources allocated during the test: 4GB ram and 75% CPU. I still checked with the standard one, i.e. 256MB ram and 50% CPU - with ".tar" format it extracts just as fast.

  • Temporarily disable log_errors in php.ini

    0 Votes
    5 Posts

    @micmc yeah, most likely it's the app. Maybe just grep through the code for errors.log ?

  • CLI points to php8.1 although PHP8.2 is set

    0 Votes
    5 Posts

    I see. Thank you for the explanation. I wasn't aware of the Ubuntu-specifica.

  • 0 Votes
    14 Posts

    great, now you can mark this as a question/solved from the top post menu.

  • How to run AI models in LAMP App

    6 Votes
    13 Posts

    If you don't care to use the proxy features in LAMP via Apache2, you can launch the App-Proxy app from the App Store and configure it on a new subdomain to proxy to any of the LAMP installed apps on local ports via the internal Cloudron IP, ie. (make sure to use HTTP and not HTTPS).

    You can get the internal IP from the web terminal by typing hostname -i

  • PHP8.1 outdated (PHP v8.1.19 current)

    0 Votes
    5 Posts

    @girish said in PHP8.1 outdated (PHP v8.1.19 current):

    I assume you are asking this for security reasons.

    Hey @girish. Thanks for your reply. Actually it depends!

    For MySQL: It's a matter of running not into backup import/export stuff or facing data losses because of some DBMS bug. So there I just prefer to having a up2date DBMS because in the past I faced one or two major issues with productive software where patching the systems could have prevented it.

    For apache2: Yes, I think no application really relies on the version nor it's super likely to hit a bug in it. Of course I faced apache2/nginx module bugs in the past but that's quite rare. Nevertheless it would help to have an up2date version at that point as well to prevent cases like that and sometimes security issues are fixed there as well.

    For PHP: Indeed this is the most relevant part for your deployed websites. In the past I just had to care about major PHP releases; minor versions never broke anything for me and had never been a requirement for any software I saw. Of course, security matters here as well.

    Thanks for clarifying which software of LAMP is managed by the platform/OS and which is managed by Cloudron itself. That gave a better insight for me.