Cloudron Forum

I'm not sure if I'm understanding correctly, but I used to use something like this in "Nginx Proxy Manager" before I discovered that Cloudron would do the same job without double the footprint:

proxy_hide_header Upgrade;
proxy_hide_header X-Powered-By;
add_header Content-Security-Policy "upgrade-insecure-requests";
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "1; mode=block" always;
add_header X-Content-Type-Options "nosniff" always;
add_header Cache-Control "no-transform" always;
add_header Referrer-Policy no-referrer always;
add_header X-Robots-Tag none;

These days Cloudron app proxy works 99% of the time out of the box (no added security or fiddling) with added bonus of being hidden behind Cloudflare IP protection, but occassionally it does not.

As of late, I've been having great difficulty figuring out how to pass "localhost:port" from my macOS device to Cloudron hosted on my NAS at a separate IP address without triggering browser security that ends up breaking whatever I'm trying to view through the reverse proxy. The code above did not work in Cloudron nor help with this issue.

@joseph Thank you and yes, did all those, and was in communication with tech support. The issue is actually mysteriously resolved and I'm just trying to figure out what happened so I can share that in this thread and hopefully avoid repeating this issue in the future.

How do we install an app like this in Cloudron when it is not in the app store? I typically host docker apps on my NAS (QNAP Container Station) and then reverse proxy via Cloudron to those apps. I host Cloudron via a VM on the same NAS. What is the advantage to hosting open-webui natively within Cloudron versus as a docker contain and reverse proxying to it?

@girish said in Should ollama be part of this app package?:

Local ollama is now integrated. You have to reinstall the app though.

Keep your expectations in check. It probably won't work great if you don't have a good CPU and we have no GPU integration yet. It's very slow with low end CPUs. I am not an expert on the RAM/CPU/GPU requirements. Feel free to experiment.

I have been using the workaround of disabling local Ollama with the Cloudron app and running a separate (external) docker container installation of Ollama with a dedicated GPU on the same hardware and then linking that instance of Ollama to the Cloudron instance of Open-WebUI. Somehow, this configuration is faster on a NAS purchased in 2018 with an add-on NVIDIA 8GB GPU than my M1 MacBook Pro with 16GB RAM and integrated GPU purchased more recently. The additional bonus of running the Cloudron Open-WebUI vs the localhost version on my Apple silicon MBP is that I can use my local LLMs on my mobile devices in transit when my laptop is shut down.

I am a long time Cloudron customer because I value your work. This is the first time I have run into an issue that I could not resolve on my own through the outlined steps offered in the Cloudron troubleshooting page. I am at a loss at how to fix this issue.

I am wondering if there is an issue with the local DNS configuration or some change that happened as the result of an automatic update that I'm unaware of as I'm getting the Cloudron DNS errors when trying to login to my Cloudron admin panel and Cloudron apps. I have SSH'd into my Cloudron VM installed on my home NAS and am able to do so via internal ip range on my home network.

This issue did follow any changes that I made on the VM itself (Ubuntu 22.04 server), nor at the Cloudron admin ("my.cloudron.adminpage"), nor at Cloudflare that hosts my domain/DNS entries. Can anyone point me in the right direction for troubleshooting steps or steps to fix local DNS assignment on Ubuntu Server 22.04? Wondering, are there Cloudron tech/customer support representatives here that read these messages?

My box.log file shows that my apps are running:

2024-06-30T00:00:10.328Z box:apphealthmonitor app health: 10 running / 2 stopped / 3 unresponsive
2024-06-30T00:10:00.009Z box:network/generic getIPv4: querying ipv4.api.cloudron.io to get server IPv4
2024-06-30T00:10:00.557Z box:dyndns refreshDns: no change in IP. ipv4: xx.xxx.xxx.xx ipv6: null

@Dont-Worry Have the logo not appearing and advanced settings not saving issues been resolved since the time of your posting here?