swiftwave icon indicating copy to clipboard operation
swiftwave copied to clipboard

bug: Can't Verify domain DNS if https redirect is setup

Open that0n3guy opened this issue 9 months ago • 4 comments

Describe the bug

I put on 2 domains, the first one I couldn't get to verify until I cleared the server cache and rebooted swiftwave. (You talk about cache here: https://github.com/swiftwave-org/swiftwave/issues/945#issuecomment-2295107048)

The 2nd one wouldn't verify no matter what I tried... until I disabled https redirect:

Image

After I disabled that, my domain verified right away and I could re-enable it.

Are you working on this issue?

No

that0n3guy avatar Mar 23 '25 13:03 that0n3guy

Can you replicate the scenario once more and send the haproxy configuration ?

It will be in /var/lib/swiftwave/haproxy folder

Remove any personal info from config

tanmoysrt avatar Mar 23 '25 15:03 tanmoysrt

Ok, I was able to reproduce.

Steps to reproduce:

  • Add a domain to swiftwave that is NOT yet pointed at your swiftwave IP (so obviously DNS verification should fail here)
  • add an ingress rule pointing at any app
  • Enable https redirect on the ingress rule
  • setup your dns to point that domain at your swiftwave IP
  • wait
  • flush cache.
  • listen to music
  • try to verify DNS. It won't work.
  • disable https redirect on the ingress rule
  • Now verifying dns will work.

Here is my cleaned HAProxy config. The domain that would not verify is wave.something.com. I downloaded this when the ingress rule was active and w/ https redirect still enabled... AND dns would not verify.

that0n3guy avatar Mar 24 '25 13:03 that0n3guy

Thanks for the reproducable steps. Will check

tanmoysrt avatar Mar 24 '25 19:03 tanmoysrt

Able to reproduce the issue, did a small fix. Will release after some testing in coming week

tanmoysrt avatar Apr 05 '25 13:04 tanmoysrt