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


Skip to content
  • 10 Votes
    8 Posts
    657 Views
    32463

    Quick update to let you know that further testing resulted in some tweaks (will update main post soon) and that sadly email and anything needing different ports still does not work even through the magic of Tailscale 😕

    TL;DR: Yes, you absolutely can run Cloudron through Tailscale (and plain-ol Wireguard too); No, it's not perfect and things that need different ports to 443 will likely not work without additional iptables tweaks if at all

  • Two Cloudron servers on same public IP?

    Support
    3
    0 Votes
    3 Posts
    433 Views
    S

    @girish Thanks for responding so quickly! I'll need to revisit my DNS knowledge to get that up and running. Doesn't seem too crazy to do. Thanks for the link, and also for actually trying to answer Daniel's question inside your link. Too many times people say "just don't do that" or, "do this other thing instead". Drives me insane 🙂

  • Url forwarding

    Locked Solved Support
    22
    0 Votes
    22 Posts
    2k Views
    C

    @nebulon Yes, there was an other port open on the raspberry - possibly from old services running on this device. But after reinstallation it was gone...

    So then I just posted the default generated nginx config for two subdomains. But I get it, that those includes are quite confusing... I try to create a cleaner version.

    Thank you for your patience.

  • Nginx in front of cloudron install.

    Support
    10
    0 Votes
    10 Posts
    1k Views
    girishG

    @danielreyes61 If you want to use nginx directly, you should make it do https proxying and not http. nginxproxymanager seems to have generated something like this:

    # ------------------------------------------------------------ # paste.cloudron.space # ------------------------------------------------------------ server { set $forward_scheme https; set $server "45.63.93.50"; set $port 443; listen 80; listen [::]:80; listen 443 ssl http2; listen [::]:443 ssl http2; server_name paste.cloudron.space; # Let's Encrypt SSL include conf.d/include/letsencrypt-acme-challenge.conf; include conf.d/include/ssl-ciphers.conf; ssl_certificate /etc/letsencrypt/live/npm-2/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-2/privkey.pem; access_log /data/logs/proxy-host-2_access.log proxy; error_log /data/logs/proxy-host-2_error.log warn; location / { # Proxy! include conf.d/include/proxy.conf; } # Custom include /data/nginx/custom/server_proxy[.]conf; }

    And proxy.conf is like this:

    set $upstream $forward_scheme://$server:$port$request_uri; add_header X-Served-By $host; proxy_set_header Host $host; proxy_set_header X-Forwarded-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header X-Real-IP $remote_addr; proxy_pass $upstream;

    Just pasting them to give you some ideas.

  • 5 Votes
    13 Posts
    2k Views
    girishG

    @necrevistonnezr yeah, we get around 3 such posts every day. Some of them are hard to figure whether they are bots or not. Like this account has been there since 2021. I actually think it's real humans but they are spamming for unknown reasons (I don't get what or who gains from this).

  • Cloudron and Apps Behind a Proxy

    Solved Support
    31
    0 Votes
    31 Posts
    3k Views
    A

    I'll create a new thread on this topic.