Using Cloudflare as a reverse tunnel with proxy manager to my Nextcloud in LXD containers in Proxmox

ℹ️ Support
,
1

Hey Guys, I’ve saw a lot of posts about people saying that Nextcloud should be running Apache and not NGINX for the proxying. Nextcloud is already running locally fine. And it’s Apache that’s currently running it soo I’m pretty sure adding NGINX would cause an issue with ports as it directly conflicts. Is there much difference between a gui version and a container in Proxmox that only has the config via shell? Secondly does anyone have a specific config they can share with placeholders that I can use to run the reverse tunnel through cloudflare? Any help with this that will simplify my setup will be deeply appreciated.

2

Hi Joshua_Christie,

Let me start helping you by making your text readable…

What is your actual situation?

Why would you want to make things more complex by adding Cloudflare?

What is your goal?

3

I don’t want to make things more complex however, all i have access is to the nextcloud at home. and due to my double nat situation it would make the address to point to my domain impossible to share anything with others or myself.

4

Ah, that is nasty :frowning:

My only conscious experience with Cloudflare consists of

  • warnings because they decrypt your traffic,
  • complaints about 100 MB file limit,
  • forum posts asking why it does not work and
  • of course now and again a broken website that only shows the Cloudflare placeholder.

There will be some FUD mixed in, but the first of these is enough for me not to touch or advice using Cloudflare, although I’m sure other opinions exist.

Would you be in a position to fork out a euro/dollar/currency per month for a VPS that acts entrypoint for your infrastructure at home? You would run a light distro on that with Wireguard, and forward all traffic to your Nextcloud server at home.

I recognize my suggestions don’t help you with concrete steps to solving your problem at this moment.

Point for point, referring to your first post:

  • Running Apache as webserver does not preclude running nginx as reverse proxy, so you could just go ahead with that (you’d run nginx on port 80/443, and forward traffic to ports of your chosing. You’d configure Apache to listen on those ports)
  • I’m not sure what you mean with “difference between a gui version and a container in Proxmox”; for what I think you mean, the only difference is the way you access the configuration of something