Skip to content

Conversation

@z0rrn
Copy link
Contributor

@z0rrn z0rrn commented Dec 5, 2025

Next to TCP 443 also expose UDP 443 port so that caddy can accept HTTP3 connections. HTTP3 is enabled by default in Caddy.

Copilot AI review requested due to automatic review settings December 5, 2025 22:53
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds UDP port 443 exposure to the Caddy deployment configuration to enable HTTP/3 support, which is enabled by default in Caddy and requires UDP connectivity.

  • Adds a new port specification for UDP protocol on port 443 alongside the existing TCP configuration

* expose udp port 443 for caddy to support new HTTP3
@z0rrn z0rrn force-pushed the caddy-expose-443-udp branch from 2a1081a to 420bf7c Compare December 6, 2025 11:31
@z0rrn
Copy link
Contributor Author

z0rrn commented Dec 6, 2025

I now tested this and this change works perfectly and allows HTTP3 requests.

@z0rrn z0rrn changed the title feat(caddy): expose 443/udp port for HTTP3 feat(uc/caddy): expose 443/udp port for HTTP3 Dec 6, 2025
Added a comment to clarify the purpose of the UDP port configuration.
Copy link
Collaborator

@tonyo tonyo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Added a comment in the code since HTTP/3 is still a pretty new thing.

Overall LGTM, the only issues I can think of is an additional (and probably unexpected for some users) attack surface, e.g. making public-facing uncloud hosts more susceptible to UDP-Based DDoS Attacks. IMO not something we should worry too much about right now though; incidentally there's a recent discussion specifically about DDoS concerns: #207

@psviderski wdyt?

@psviderski
Copy link
Owner

Yeah, this sounds good to me 👍

@psviderski psviderski merged commit 4b4b721 into psviderski:main Dec 8, 2025
4 checks passed
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

Successfully merging this pull request may close these issues.

3 participants