Hi All, I encountered a weird issue and I am stumped what could be going on.

I spun a cloud vm and installed docker, then proceeded to install portainer for ease of use.

I installed the two necessary containers for this instance , Nextcloud AIO and NGINX Proxy Manager.

I followed https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md

But for some sort of weird issue I could not connect with the reverse proxy to the nextcloud instance.

Even when i resorted to the nginx shell the localhost:11000 the place where nextcloud apache is hosted could not be resolved.

Managed to gain access to the container by using the docker virtual ip of the apache container, but i see this as no solution because the virtual ip can change whenever an update is applied.

I appreciate your views and solutions :)

You are viewing a single thread.
View all comments
1 point

Short and easy answer is switch to ”Caddy” search for caddy reverse proxy. Best thing i have ever used in terms of proxy 😁

permalink
report
reply
1 point

That will not solve OPs problem.

permalink
report
parent
reply

Self-Hosted Main

!main@selfhosted.forum

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

For Example

  • Service: Dropbox - Alternative: Nextcloud
  • Service: Google Reader - Alternative: Tiny Tiny RSS
  • Service: Blogger - Alternative: WordPress

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

Community stats

  • 23

    Monthly active users

  • 1.8K

    Posts

  • 11K

    Comments

Community moderators