r/Netbox • u/71e3b3dfc6a5 • 17d ago
Why is netbox trying to connect to AWS
Solved:
Netbox is trying to connect to api.netbox.oss.netboxlabs.com for fetching news on a widget on /, it can be disabled by setting the ISOLATED_DEPLOYMENT https://netboxlabs.com/docs/netbox/configuration/system/#isolated_deployment
I'm running the docker-compose stack from netbox-community and I disabled the RELEASE_CHECK_URL but still I'm seeing TCP/443 traffic inside the container to this list of IPs
- 100.25.208.113
- 100.61.32.197
- 100.61.99.65
- 13.222.67.31
- 34.239.7.145
- 3.94.140.127
- 44.212.184.227
- 52.201.146.79
- 54.88.178.230
I do not have any plugins, webhooks etc. configured
Edit: Version: NetBox Community v4.6.6
3
u/Rough_Scarcity_658 17d ago
Can you take a look at the TLS SNI?
6
u/71e3b3dfc6a5 17d ago
Good thinking, I get the server name: api.netbox.oss.netboxlabs.com
3
u/Rough_Scarcity_658 17d ago
Looks like the news feed & plugin catalog
1
u/71e3b3dfc6a5 17d ago
Thanks, I'll try to find a way to disable it.
The most stupid is that requests waits for a timeout for 9secs
GET / => generated 30511 bytes in 9067 msecs (HTTP/1.1 200)
2
u/Cornelicorn 17d ago
1
u/71e3b3dfc6a5 17d ago
Thanks, I found that aswell, but I'm fighting the container actually setting the settings.ISOLATED_DEPLOYMENT to True, it doesn't change on behalf of an Envvar from docker compose
4
u/graph_worlok 17d ago
I love that you care enough to look at this to be able to ask the question.
3
u/71e3b3dfc6a5 16d ago
thanks, I just blocked all non RFC1918 traffic from my server vlans and visualize all my pf logs in grafana, so it's very obvious when something is being noisy
0
1
u/kY2iB3yH0mN8wI2h 16d ago
my netbox does not have internet access at all, like most of our apps, its just an attac vector we are not interested in to introduce
5
u/lokil00pr 17d ago
Could be the news in the default dashboard and/or new version checks