this post was submitted on 17 Oct 2023
3 points (100.0% liked)

Self-Hosted Main

515 readers
1 users here now

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

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

founded 1 year ago
MODERATORS
communick@selfhosted.forum
3
Help With NPM IP Weirdness On Synology (alien.top)
submitted 1 year ago by Volitanic@alien.top to c/main@selfhosted.forum
2 comments fedilink hide all child comments
 

I'm having issues with my new NPM setup. I'm 1 day in to NPM so I'm very new.

Anyways, I have NPM on a macvlan on my Synology and it's responding on the correct ip 10.10.10.200 on ports 80 and 443.

I have a speedtest tracker container on its own bridge network. NPM is also connected to the speed test network and can see the container at speedtest:80.

I have a cname on my pihole for my speedtest tracker container pointed to the NPM ip. So speedtest.me.home cname points to NPM ip of 10.10.10.200. NPM forwards this to speedtest:80 just fine.

The issue I have is that I have another container, homepage, on the default bridge network that queries the speed test API and it's failing. In the logs, it seems like the query returns the NPM ip of 10.10.10.200 for some reason. However, when I copy and paste the API URL into my browser, I see what I'm expecting.

So, what the heck? Why is the homepage container querying speedtests API not working when I can see the API results on my browser?

Does anyone know where I can start looking to track this down?

you are viewing a single comment's thread
view the rest of the comments
[–] Gavlester@alien.top 1 points 1 year ago

Is your homepage using the host ip (Synology IP)?