HTTP V4 TO V6 PROXY CODE

The proxy will happily redirect requests to either http or https to the Pi, but this results (without turning on the Proxy Protocol) with getting remote addresses in your logs of the proxy servers, which is not entirely useful. If u open you will see a 400 error and the port failure.So, more because I was intrigued than anything else, I've got a pi3 from Mythic Beasts, they're supplied with IPv6 only connectivity and the file storage is NFS over a private v4 network. Lets run on one Server a Webserver like apache2 and on the other caddy as reverse proxy: Add a domain like to the public IP of the caddy Server. Give both server a ULA ipv6 address that they connected directly and give the caddy2 Server a public v6. Tutorial (minimal steps to reproduce the bug) caddy2_beta13_linux_amd64 reverse-proxy -from :443 -to test.dns:80 I can use a fqdn and it works cat /etc/hosts caddy2_beta13_linux_amd64 reverse-proxy -from :443 -to :80Ĩ 23:15:54.761 WARN admin admin endpoint disabledĨ 23:15:54.762 INFO http server is listening only on the HTTPS port but has no TLS connection policies adding one to enable TLS Ĭaddy 2 proxying from to sorry no more logs from caddy 2d. I can not use v6 address in the to parameter at reverse proxy 2c. It seems that der Port in the last line is the number from the last 2 bytes of the ip address:

Your browser sent a request that this server could not understand.Īdditionally, a 400 Bad Request error was encountered while trying to use an ErrorDocument to handle the request.Īpache/2.4.38 (Debian) Server at Port 204 I not use any config file and use only this line on caddy What happens (briefly explain what is wrong) Go version (if building Caddy from source run go version) V2.0.0-beta.13 h1:QL0JAepFvLVtOatABqniuDRQ4HmtvWuuSWZW24qVVtk= 1c. Caddy version (run caddy version or paste commit SHA) The Apache2 Server has fd1f:4614:ef30::204/64 as IPĭomain to a AAAA record to the public IP of the first Server. The Caddy2 Server has fd1f:4614:ef30::203/64 as IP and a public IP where we can connect from the internet 😞 Only actionable issues are kept open, and if there is not enough information or clarity to reproduce the bug, then the report is not actionable.Įxample of a tutorial: Create a config file:ġ.

Note that ignoring this advice may result in delays, or even in your issue being closed.

Domain names are public knowledge and often necessary for quick resolution of an issue!

Do not redact any information from your config (except credentials).

Use a simpler HTTP client instead, like curl.

If making HTTP requests, avoid web browsers.

Run Caddy manually in your terminal do not use systemd or other init systems.

Add only the lines/parameters that are absolutely required to reproduce the bug. You are writing a tutorial, so make sure to carry it out yourself before posting it. Tutorial: What are the minimum required specific steps someone needs to take in order to experience the same bug? Your goal here is to make sure that anyone else can have the same experience with the bug as you do. This can add crucial context to your report.

2e) Relevant links: Please link to any related issues, pull requests, docs, and/or discussion.

2d) Workaround: What are you doing to work around the problem in the meantime? This can help others who encounter the same problem, until we implement a fix.

DO NOT REDACT INFORMATION except for credentials.

HTTP V4 TO V6 PROXY CODE

2c) Log output: Paste terminal output and/or complete logs in a code block.

What happens? Why is it a bug? Not all bugs are obvious, so convince readers that it's actually a bug.

(They are always relevant.) If you built Caddy from source, provide the commit SHA and specify your exact Go version.ĭescription: Describe at a high level what the bug is. Tutorial (minimal steps to reproduce the bug)Įnvironment: Please fill out your OS and Caddy versions, even if you don't think they are relevant. Go version (if building Caddy from source run `go version`) Caddy version (run `caddy version` or paste commit SHA)

Http v4 to v6 proxy