I could reach every other relay, tho, and I've never gotten that error. I publish books all day, every day.
Discussion
and the relay operator and developer also has confirmed an issue, both with the reverse proxy (502) and the not being able to get results back, as they are simply not stored on the relay
plus, fiatjaf's nak tool doesn't have a timeout when the relay doesn't respond in a timely way
DNS resolution failure. The relay is fine and it works for me.
Often what I experience is DNS resolution fails due to packet loss.
The error is not you but your network
Anyway, since the relay is experimental and was moved to a new server, you will need to re-broadcast events (DB was not moved)