mirror of
https://github.com/fosrl/olm.git
synced 2026-03-08 23:03:12 -05:00
Can ping Pangolin site but not curl any resource #17
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @catch-404 on GitHub (Sep 23, 2025).
Hi, I'm trying to setup what crowdsec calls a multi-server setup with Pangolin.
The idea is that the "local" crowdsec API server lives on one machine (the Pangolin VPS in my case), and another crowdsec instance runs on a remote machine (in my case, my NAS at home). The latter doesn't use its own local crowdsec API but instead connects to the remote one on the other machine.
The reason for doing this is that I can use my NAS as a crowdsec log processor, that would read logs from my different services running on that machine, and send them to Pangolin's crowdsec instance for the api over there to do its thing.
I want to use olm to create a tunneled connection from the NAS to the VPS and connect the NAS's crowdsec instance to the VPS's via the tunnel, and thus avoid exposing crowdsec's port 8080 publicly.
So, I installed newt on the pangolin instance to create a site on the VPS, with
ACCEPT_CLIENTS=true.I created an olm instance on the NAS, and changed the NAS crowdsec instance to go through olm's network stack.
On the NAS, running
docker exec crowdsec ping [newt_vps_ip]works just fine, butdocker exec crowdsec lapi register --machine NAS --url http://[newt_vps_ip]:8080does not.docker exec crowdsec curl [newt_vps_ip]:8080doesn't either.I had port 8080 opened temporarily on crowdsec on the Pangolin-hosted VPS throughout my attempts, and I could verify that from the NAS's crowdsec instance, both
docker exec crowdsec lapi register --machine NAS --url http://[vps_ip]:8080anddocker exec crowdsec curl [vps_ip]:8080work.On the Pangolin-hosted VPS,
docker exec [container] curl crowdsec:8080works from all containers.So I'm a bit lost, I don't really understand how I can ping the VPS through the tunnel but not curl anything running there this way.
Am I missing something?
For reference, here are my compose yaml on both servers:
NAS
VPS
@AstralDestiny commented on GitHub (Oct 19, 2025):
Shouldn't have crowdsec ports open to the world remove the ports or slap a 127.0.0.1:8080:8080, 127.0.0.1:6060:6060 on there it can still talk over docker networks but both of those crowdsec's ports aren't meant to be public.. You could run a gerbil and such on both sides though but until Owen fixes some olm stuff I can't really guide you through the olm stuff.
@catch-404 commented on GitHub (Oct 19, 2025):
Yes I know, I removed both ports, that was just for the test. Not sure I really want to mess around trying to hack this with another pangolin/gerbil stack, I don't understand enough of it to attempt it tbh.
Eventually I might just use tailscale for this, but it would be cool to see olm work for this usecase, as I could rely on pangolin/fossorial stuff only
@AstralDestiny commented on GitHub (Oct 19, 2025):
Can guide you through my method on the discord trivially if you so desired. https://discord.gg/MZtgvEfNCc