Repository navigation
Getting error that port 80 is already in use. It is because I'd like to install this on the same VPS where I have Pangolin installed. #134
Description
Basically just the title. I have Pangolin installed on my VPS for my reverse proxy. I'd like to install rybbit here too but since Pangolin is already using port 80, is this not possible?
Activity
poliroid commentedon May 7, 2025
It is possible.
By default rybbit installs web server (Caddy), you dont need it.
Use Documentation -> Self-hosting -> Advanced for your setup.
Looks like
--no-webserverparam is what you need.jonzey231 commentedon May 7, 2025
Got it. Thanks!
jonzey231 commentedon May 7, 2025
I got it setup and can access my tracking.domain.xyz/signup to get everything setup. I enter my name, email, and password and it doesn't respond when I click continue.
smileBeda commentedon May 9, 2025
@jonzey231 try this:
https://www.rybbit.io/docs/self-hosting-advanced#docker-compose-setup-with-npm-without-exposing-ports
It should allow you to set it up along with tons of other services without any hassle
The "does not respond" issue is most likely due to missing clickhouse config, OR missing rewrite for the API (see doc I linked it explains everything)
serversathome-personal commentedon May 10, 2025
@smileBeda i have a similar issue and i think its due to when ppl use either pangolin or CF tunnels the docker compose is assuming
npmand that step 5 from the doc listed (Make sure to create your external network npm_proxy and make sure NPM is on it as well) is true, but it will not be for someone running a different reverse proxy than npm.the challenge is getting a docker compose setup where i can simply forward port 3002 and nothing else, and not need any external networks in the compose file.
smileBeda commentedon May 10, 2025
Well, you can use any external network as a matter of facts.
The key is that the container on which Rybbit runs can talk to the proxy you use.
If you use CF Tunnel, you still need some proxy like Caddy afaik, so you would just ensure Caddy and Rybbit are on the same network.
You could also use ports of course and host network but that opens your hosts guts to the world, so that I would not suggest.
Docker natively operates in a way where if you map ports, it opens them to the outside, and you do not want that.
This is why a proxy should be used, and docker networking, to not force the port usage.
Hope that makes sense!
And yes, the section is assuming NPM, but in the end NPM is just an nginx proxy
There's a contributor who shared their traefik setup here #135 (comment)
Maybe that helps deducting setups for other proxies?
serversathome-personal commentedon May 11, 2025
@smileBeda i think the goal would be to eliminate caddy entirely.
for most self-hosters, we already have something in place and just want you to expose a port i can hit. by trying to route traffic within the stack, its breaking all the ways i already route traffic, and there is more than one option so really all i need is a docker compose stack (with possible an env file but preferably not) with a single port i can target from CF tunnels or NPM or pangolin or tailscale.
smileBeda commentedon May 11, 2025
By my understanding that's exactly what you can do and both the examples I linked and the "official" nginx example do.
They target 2 ports instead of one, yes. Is that the issue? Can't you write two tunnel rules with cf? I only used Argo once, but as far I recall it should be entirely possible?
I've never used pangolin, but it is a reverse proxy, so should also be able to do this?
Rybbit doesn't open port 80, when not using it with caddy
So it should be entirely possible to use it with any proxy?
serversathome-personal commentedon May 12, 2025
@smileBeda eh, two ports isnt ideal. for something like CF tunnels, each port would need a FQDN and i dont think your compose stack is setup to receive traffic like that.
pangolin is the self-hosted version of CF tunnels (basically).
the idea for self hosters would be not to have to have the docker compose stack on the same docker network as the reverse proxy bc not all of us will be running both on the same machine. for example, if i wanted to setup your software in a proxmox LXC, that will never be able to docker network to where my NPM is....
smileBeda commentedon May 12, 2025
Ok, I understand what you mean now..
So I guess the only current workaround would be to keep caddy and change the caddy port instead if it conflicts, and then route your external requests to that?
In any case I think this is indeed a valid request given the circumstances you explain.
Leaving this for @poliroid or @goldflag for further assessment
serversathome-personal commentedon May 12, 2025
@smileBeda @poliroid @goldflag
my dream scenario would be no need for caddy at all. i will tell you why:
i consider myself a pretty average homelabber. i have 3 different connection profiles for my stuff: NPM, CF Tunnels, and Netbird. I use whichever is best for whatever solution I am deploying. Right now there is no way for me to host rybbit due to the fact that it either:
as such, to host this, I would want to use it without the webserver, using one port for incoming connections, and not dependent on being on the same machine or network as my existing rev proxy solutions.