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

Switch mqtt vehiclepositions port to 443 #85

Open
hbruch opened this issue Jan 4, 2025 · 6 comments
Open

Switch mqtt vehiclepositions port to 443 #85

hbruch opened this issue Jan 4, 2025 · 6 comments
Assignees

Comments

@hbruch
Copy link
Contributor

hbruch commented Jan 4, 2025

City of Herrenberg seems to block ports other than 80 and 443. Especially vehiclee positions can't be displayes from inside the Herrenberg network.

Please check, if the mqtt service can be switched to use port 443.

@leonardehrenfried
Copy link
Contributor

It's already on port 443 but using the websockets protocol.

image

Is that maybe blocked?

@hbruch
Copy link
Contributor Author

hbruch commented Jan 6, 2025

Hm, that might be.

If mqtt is already served via 443, these firewall allowed ports are outdated and can be removed?

@leonardehrenfried
Copy link
Contributor

Port 1884 we can close, yes. The others are occasionally useful for debugging the raw mqtt topics.

@hbruch
Copy link
Contributor Author

hbruch commented Jan 21, 2025

@stadtnavimanager vehicle positions are already sent via Port 443. If the municipal firewall filters the mqtt protocol (as it seems), these firewall rules need to be changed.

@leonardehrenfried
Copy link
Contributor

leonardehrenfried commented Jan 21, 2025

To be precise, it's not the MQTT protocol that we need but Websockets which MQTT is multiplexed over.

@stadtnavimanager
Copy link

I forwarded the link to this issue to our IT and hope to get support soon.

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

3 participants