Closed jdeg closed 1 month ago
If you change the port you publish on the host, then you have to use that port when you make a request. Do curl -v https://dev.website-review.drt.localhost:59708/
Keep in mind that if you use non-standard ports, the ACME HTTP and TLS-ALPN challenges will not work (you must use ports 80 and 443 for those challenges) so you wouldn't be able to get publicly trusted TLS certs.
Perfect, thank you very much.
Issue: Changing Default Caddy Ports for Serving Local Drupal Environments
I have an application Dresktop that creates local Drupal environments. I use Caddy to serve over HTTPS and provide friendly URLs. I want to enable users to configure alternative Caddy ports in case ports 80 and 443 are already in use.
To test this, I tried running a httpd container on port 80 and configured Caddy to use alternative ports. Here's my setup:
and this is docker compose configuration file
The idea is to use dev.website-review.drt.localhost and access the Drupal environment, but I get this when I test it wih Curl
I’ve tried several Caddyfile configurations but keep encountering the same issue. I'm not sure if the issue lies in the Caddyfile, the Docker Compose setup, or something else.
Is there something I’m missing in my configuration to successfully change the Caddy ports and access the Drupal environment using the alternative ports? Thanks in advance.