Cloudron Forum

Thank you! I will test this following your clarification.

@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.

I did not see any mention of this on the Cloudron docs page for MiroTalk and hopefully this is a simple initial setup question:

Does the warning about disabling Cloudflare proxying on the app's Location settings page also mean that I need to port forward to port 40000 per the default settings?

Locations
subdomain.mycloudron.com

SFU TCP Ports (100 ports) 40000 to 40099
40000
Cloudflare proxying must be disabled for the app's domain to access this port

SFU UDP Ports (must be same as TCP ports) (100 ports) 40000 to 40099
40000

Cloudflare proxying must be disabled for the app's domain to access this port

@girish What is the location of the Cloudron log that would have observed any changes that were observed when I was able to use Cloudron again? Or is this an error log located at the Ubuntu Server (Virtual Machine, v24.04) level?

I will update this post with that information if I can find what changed for Cloudron to be available again, as the only change I can think of was doing a disk permissions fix to the "shared folder" that the VM is installed on the RAID configuration on my home NAS hardware. That seems like a very imprecise and not very helpful "resolution" to the issue related to this thread for archival (support) purposes.

To anyone following this thread, I have good news and bad news:

Good news: My issue is resolved. I am now able to log into my Cloudron Dashboard and apps at their respective subdomains, and Cloudron reverse proxying to my Docker apps/containers hosted outside of Cloudron.

Bad news: I tried every troubleshooting angle that I could find both via my own research, via Cloudron tech support, and through ChatGPT by unloading my error logs and step by step troubleshooting at the CLI/terminal level of my Ubuntu Server VM layer. Nothing worked.

Last night as a semi-regular part of my digital housecleaning and maintenance, I ran a disk permissions fix on my home NAS where the Ubuntu Server VM --> Cloudron resides and next thing I know, I received an email from @girish with a screenshot of my Cloudron Dashboard loading. 🧐

Are there any particular Cloudron or Ubuntu Server error logs that I might be able to throw into ChatGPT to figure out what happened so I can report back here?

@girish I have gathered the information you requested and responded via email. I would really like (need) some live assistance from a support person.

@girish Thank you! I downloaded the Cloudron support diagnostics through terminal and emailed them with the link to this support forum post and the diagnostics / logs + my Cloudron ID. Hopefully I will hear back from someone soon.

@girish what is best way to get some support with this issue from customer/tech support?

@nebulon Does not work when disabling cloudflare proxying.

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

@girish Thank you! This is one of those functionally insignificant but aesthetically extremely significant updates. I really appreciate you figuring this one out. Great work!

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

@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.

@Kubernetes I am not sure if this is what you are asking, but I am currently running Ollama separately via docker with a dedicated OLD GPU (8GB NVIDIA) on my NAS (working shockingly good on 7B/11B GGUFs and moderately good on 13B ones) and Cloudron on a VM on the same NAS. I use Ollama externally (technically it's still local on the machine's hardware, but is configured as though it is not) and deactivated this app's localhost Ollama. This can be done by going into the Cloudron's Open-Webui File Manager through the settings and configuring "env.sh" -

# Change this to false to disable local ollama and use your own
export LOCAL_OLLAMA_ENABLED=false

# When using remote ollama, change this to the ollama's base url
export OLLAMA_API_BASE_URL="http://changethis:11434"

# When local ollama is enabled, this is location for the downloaded models.
# If the path is under /app/data, models will be backed up. Note that models
# can be very large. To skip backup of models, move the models to a volume (https://docs.cloudron.io/volumes/)
# export OLLAMA_MODELS=/app/data/ollama-home/models

Is this what you are referring to?

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?

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.

@doodlemania2 Are you still sharing access to the Nextcloud Talk high-performance back-end that you have created? If so, how may I contact you to test it?

Must we install ImageMagick/Imagick on our server hosting Cloudron in order to have PDF previews function correctly or are ImageMagick/Imagick installed as part of the initial Cloudron installation script during the original setup? I am using Ubuntu 20.04 and Cloudron installed on a VM located on my home NAS.

With gratitude,
James