Two findings on /setup/domain/. First, the domain field rejects host:port with 'Enter a valid domain' — a dev or non-443 deployment cannot enter the host it is actually served on. Second, the panel says the challenge 'expects the body to be:' followed by an empty grey box; the expected token never renders, so an operator cannot create the file the check wants. The second makes HTTP domain verification unusable as shipped. Found in the #127 browser pass.
Two findings on /setup/domain/. First, the domain field rejects host:port with 'Enter a valid domain' — a dev or non-443 deployment cannot enter the host it is actually served on. Second, the panel says the challenge 'expects the body to be:' followed by an empty grey box; the expected token never renders, so an operator cannot create the file the check wants. The second makes HTTP domain verification unusable as shipped. Found in the #127 browser pass.