1. Caddy version (caddy version): 2.4.0 2. How I run Caddy: a. System environment: Reproduced on both Windows 10 and Amazon Linux 2. b. Command: For windows caddy_win.exe run --resume For Linux sudo systemctl start caddy c. Service/unit/compose file: d. My complete Caddyfile or JSON conf…

Looks like I touched an adjacent function and made a mistake when rebasing. Fixed on master now. admin: Reinstate internal redirect for /id/ requests committed 04:27PM - 19 May 21 UTC (UTC) [mholt] …

What if you remove the spaces? Seems strange to me to be using non-URL-safe characters here (i.e. spaces; dashes are fine)

I have tried just a basic word and the one in the docs my_proxy nothing works. It definitely “finds” the ID because if I use an ID that does not exist, it gives an error complaining it can not be found. So I guess it finds the selector but it returns 0 data for it, Content-Length: 0

Okay. It’s most likely a regression introduced in this PR (cc @matt ): admin: Secure socket for remote management caddyserver:master ← caddyserver:remote-admin opened 10:32PM - 25 Jan 21 UTC (UTC) …

That would be weird, those changes have nothing to do with the actual admin handlers, or config IDs… looking into it.

That was super fast :slight_smile: thanks for the help… I have only been downloading the Caddy executable from the website because I need to include the Route53 package. How can I test this change you made, I have seen GitHub - caddyserver/xcaddy: Build Caddy with plugins being mentioned a few pla…

Yep. xcaddy build master --with https://github.com/caddy-dns/route53

Awesome thanks, I will try it tomorrow (+12hours) and let know if it worked.

@matt Thanks that worked… Guess I was the first one that upgraded and used that on the latest version then, would have thought it be more popular… What do others do then, just rewrite the whole config as opposed to what I am doing now, which is changing specific routes? OR I guess if you simple lo…

A large majority of users just use the Caddyfile and don’t make use of the API. And I would postulate that those that do typically want more stability over updating early. FYI v2.4.1 is out as of last night, which includes this fix.

[image] francislavoie: FYI v2.4.1 is out as of last night, which includes this fix. I just tried using caddy upgrade, but the version is still 2.4.0??

ID Selector is not working after upgrade to 2.4.0

Help

francislavoie (Francis Lavoie) May 20, 2021, 4:45pm 13

The build server’s build cache still hasn’t been kicked I think. See the explanation here: