Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Firewall Block because of traffic to/from ToR Network after Container start/restart? #1134

Open
haferm opened this issue Sep 25, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@haferm
Copy link

haferm commented Sep 25, 2023

Describe the bug
Since 3 days my Firewall complains about incoming?? Traffic, indicates that someone may be attempting to exploit an application's vulnerabilities. ET TOR Known Tor Relay/Router.
Always same IP: 194.36.147.125, (rs.hosting-os.de)
Port: http-alt
I am using Tag: dev
Manually Blocked this WAN IP now.

To Reproduce
Container Restart.
manual tcpdump running on firewall confirmed docker host communicating with Internet Endpoint: 194.36.147.12 just after/during startup

Context

  • OS: Debian / Docker
  • Speedtest-Tracker Version: Tag: Dev 1.12.3

Additional context
Why is this container trying to communicate with 194.36.147.125, (rs.hosting-os.de) after restart?

@haferm haferm added the bug Something isn't working label Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant