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


Cloudron private installation



  • Absolutely. And the requests which make the system hang are https too


  • Staff

    @dkdkdkk This happens with all apps? What app is office.<domain> btw?



  • Yes all apps and the cloudron admin page itself too. When app has it the others do the same at the same time. I did a complete reinstall already. Same problem.

    office= onlyoffice document server


  • Staff

    Since you said Ctrl+F5 sorts out the issue, I wonder if this is some browser caching issue (from your previous non-cloudron setup). Have you tried another browser or another device? Or maybe clear the browser cache and try.

    Depends on how deep you want to go but you can also try curl https://my.domain.com, you will only see relative URLs like https://paste.cloudron.io/juwojaqume.xml , so I am not sure where the redirects are coming from.



  • Cache has already been cleared. Tried on both firefox and opera on ubuntu and on firefox on a iphone. Mobile does not seem to suffer from this issue.

    Firefox seems to keep "hanging". Opera starts with the same issue, but recovers after ~7-8 sec and seems to do a hard refresh (which solves the problem).

    My feeling is saying that a local IP address from a DNS resolve is kind of "wrong", maybe a browser does not like that. I tried experimenting with hairpinning and that kind of stuff too.

    Update:

    I installed ubuntu directly on a system and cloudron on top. 16GB, 4 cores and 256gb storage. VM was the first thought, but installed directly to compare the behavior.

    I also installed cloudron on a EC2 instance. No problemo....


  • Staff

    @dkdkdkk said in Cloudron private installation:

    My feeling is saying that a local IP address from a DNS resolve is kind of "wrong", maybe a browser does not like that

    Generally, this is not a problem at all. In fact, that's how every intranet works (or even amazon VPC instances have DNS names that map to internal addresses). Browsers should also have no problem because otherwise every corporate which requires you to VPN in first before connecting to intranet won't work.

    I say 'generally' because maybe there are some special intranet/local IP ranges with special behavior that I don't know of.

    Hairpinning also shouldn't be a problem because we are talking of local addresses here and it should never need to exit the router.

    I think your observation that firefox keeps "hanging" is interesting. Can you quickly try host my.domain.com on the CLI ? Does it translate quickly? Do you also have this DNS over HTTP which is supposedly enabled by default in firefox? I am not sure how it influences all this. Just putting some ideas for you to debug 🙂



  • Just chiming in here, maybe someone has an explanation or solution for my problem. I have a similar setup: local server which is online but shouldn't be reachable from outside the network. The installation of cloudron was no problem, initially used cloudflare for the setup and changed to LAN IPs afterwards. Installing regular apps also works, but I'm looking forward to package a custom app, which requires me to fire up cloudron CLI after building it. But when I try to login via LAN, this happens:

    cloudron login my.cloudron.example
    Username: m
    Password: *****************
    2FA Token (if enabled): 
    write EPROTO 140479727316736:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:802:
    

    Also tried the suffix with --allow-selfsigned but no dice, anyone an idea what that's all about? All certs are there and the browser connection works fine.

    Could a temporary port forward/DMZ be the solution?


  • Staff

    @msbt There was a similar issue recently - https://forum.cloudron.io/topic/3123/handshake-faliure-when-trying-to-login-through-cli . Can you check node version and reply there?



  • ah my bad, didn't search for the error on the forums, let me try and report back asap, thanks!



  • @girish stellar service as usual, of course it was the old node version, login works as expected now!