Cloudron CLI and NGINX Routing Weirdness

[Lonkle]

@robi It has nothing to do with the VPN, the VPN has a front end client and it can be off, but even if it's off NGINX still conflicts with itself like it was in some kind of cache I couldn't find and I wanted the domain name back on the app so I re-installed.

[robi]

@Lonk never said it did.

[Lonkle]

@robi said in Cloudron CLI and NGINX Routing Weirdness:

What happens when you switch the domain to vpn2?

If I switched the domain to vpn2 it would just work. The domain name is being cached by NGINX in a way I don't understand so I just re-installed.

[robi]

@Lonk yes, you said this already.

what's different in nginx -t or other relevant place?

[Lonkle]

@robi said in Cloudron CLI and NGINX Routing Weirdness:

@Lonk yes, you said this already.

what's different in nginx -t or other relevant place?

Well nginx -t said conflicting server name "vpn.viridiancloud.com" four times or so when I used it in the command line, and since that gave me no new information I gave up. Pick your battles!

[robi]

@Lonk sigh, the question was what's different with vpn2...

[Lonkle]

@robi said in Cloudron CLI and NGINX Routing Weirdness:

@Lonk sigh, the question was what's different with vpn2...

Well, changing the location, it creates a completely new container including network / port changes. But repairing the Cloudron app, didn't fix it so it wasn't the container or the network itself. Hmm, maybe I'll still look more into this problem cause I still am curious, I just need to ask a question first on the dev forum about remote SQLing into Cloudron's App DB first before I dive further as there is one last thing I need to solve it.

[Lonkle]

Well, at least I can say with confidence that backing up, then re-installing Cloudron completely fixes the issue. But I did a full restart of the server and that didn't fix it so it's not exactly a "cache" issue. I'll do more testing since I can repoduce it.

[Lonkle]

But it could just be me, can any @appdev reproduce this:

• So you're developing an app and want to start fresh instead of cloudron update to see your app installed as a new user
• cloudron uninstall
• cloudron build && cloudron install
• Location: [same location as before the uninstall]
• NGINX gives me 503 errors and app never passes health check

If it's just me, then I have to debug this issue in a different way.

[mehdi]

@Lonk I never encountered the issue, and this is a workflow I often use. Maybe it has something to do with your networking changes on your cloudron you did for the VPN thing ?

[Lonkle]

@mehdi That’s what I’m thinking it must be - it’s happening with my VPN Client since that’s what I’ve been working. But the box code treats the OpenVPN Client like normal and only treats the apps connected to it special.....wait, what if the cache of the domain exists because an app was connected to my OpenVPN Client app so it’s still “somewhere” in memory even though technically that container is no longer referencing an active container.

That’s a great idea and I think that may be the cause. Because it would persist reboots even, the app connected to the VPN Client attempting to connect. I’m just hoping I can get some advice on how to access Cloudron’s internal app DB via Remote SQL (like you can with individual apps) so I can debug this issue entirely.

I want to release the OpenVPN Client on the store in 2021. So I gotta make sure it’s perfect - and your comment just sparked a thought process that very likely could be the problem and I was dismissing it in my head for silly reasons. Thanks. I’ll reproduce it now that I know it’s just me, and see if I can fix it.

I really just needed one other person on the latest Cloudron perform those steps and have it go perfectly for me to know it was my app (and box changes).