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

unable to connect outside #176

Open
Darkmagister opened this issue Oct 4, 2024 · 0 comments
Open

unable to connect outside #176

Darkmagister opened this issue Oct 4, 2024 · 0 comments

Comments

@Darkmagister
Copy link

Darkmagister commented Oct 4, 2024

Specifications

  • Image hash or version: 1.32.1 (and older)
  • Platform: docker on debian 12
  • Subsystem: proxmox

i installed a new machine on my lan, and moved all the container from the old server to the new one, this machine is a debian vm over proxmox, i passed the usb device to the vm, and the device to the container, i tried disabling all the service and only having fr24 but still nothing

Expected Behavior

starting the container normally

Actual Behavior

the container start but it seems unable to communicate with the outside world, i get erro to sync with ntp,
[fr24feed] 2024-10-04 11:45:40 | [feed][e]Could not retrieve configuration from Flightradar24!
[fr24feed] 2024-10-04 11:45:40 | [feed][e] Timeout was reached
[fr24feed] 2024-10-04 11:45:40 | [feed][e]Request failed, code=0
[fr24feed] 2024-10-04 11:45:40 | [feed][i]Failed on start, Sleeping 30 seconds
[fr24feed] 2024-10-04 11:46:10 | [feed][d]fetching configuration
[fr24feed] 2024-10-04 11:47:10 | [feed][e] Timeout was reached

[fr24feed] 2024-10-04 11:53:14 | [feed][n]Error: Could not connect feed! (result -1, fd -1)

the problem is that sometimes restarting the machine make it work

i'm testing now with an older version but similar result, i also tried setting the:
SYSTEM_HTTP_ULIMIT_N=1048576
SYSTEM_FR24FEED_ULIMIT_N=1048576
ULIMIT_N=1048576

but still nothing, (also i tried make the container privileged or use the host network, those made it worse)

maybe it's something on my network but what can it be ? what can i do to test it? i have multiple container and they dont seems to suffer the same issue with the network

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant