[GH-ISSUE #123] 404 on opening websocket. #86

Closed
opened 2026-02-28 14:16:17 +03:00 by kerem · 1 comment
Owner

Originally created by @iHax0rMC on GitHub (Dec 28, 2020).
Original GitHub issue: https://github.com/abh/geodns/issues/123

When opening a websocket it will give an 404 error.

I can ping the port without any problems (otherwise an 404 will not be thrown).

No difference when enabling or disabling the authentication.

Startcommand: ./geodns -log -interface ipfromserver -identifier domainfromserver -port 53 -http=":8053"

Originally created by @iHax0rMC on GitHub (Dec 28, 2020). Original GitHub issue: https://github.com/abh/geodns/issues/123 When opening a websocket it will give an 404 error. I can ping the port without any problems (otherwise an 404 will not be thrown). No difference when enabling or disabling the authentication. Startcommand: ./geodns -log -interface ipfromserver -identifier domainfromserver -port 53 -http=":8053"
kerem closed this issue 2026-02-28 14:16:17 +03:00
Author
Owner

@abh commented on GitHub (Jun 4, 2025):

Yeah, the websocket API was replaced with prometheus in v3.0.1 in 2019. :)

<!-- gh-comment-id:2939181861 --> @abh commented on GitHub (Jun 4, 2025): Yeah, the websocket API was replaced with prometheus in v3.0.1 in 2019. :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/geodns#86
No description provided.