Ordnary

Docs Ordnary Web Services Ordnary Netway

Troubleshooting

An application that stays Awaiting DNS, Action required, visitors seeing errors, and other things that go wrong, with what fixes them.

4 min readBeginner
The status stays Awaiting DNS

A record is missing or wrong, or has not propagated. The DNS & TLS tab shows which of the three is still pending. Check with dig, compare the name and value character by character, and allow up to an hour.

Action required: hostname validation failed

The ownership TXT record was not found or has the wrong value. Create it exactly as shown; the record name starts with an underscore and is specific to this application.

Action required: certificate failed

The certificate TXT record is wrong or missing, or a CAA record on your domain forbids issuance. Fix the record; issuance retries on its own.

Visitors see an error page from Netway

Netway could not reach your origin. Check that it serves HTTPS on port 443 with a valid certificate chain, answers for your hostname, and is not blocking the edge. The origin must be reachable from the internet.

My own API calls are being challenged

The hostname is on the Strict profile. Put API traffic on its own hostname with the API profile, or switch the profile. See Security profiles.

A legitimate user is rate limited

Many users behind one address, such as an office or a carrier, share the per-IP limit. Use a profile with a higher limit (API: 1200 per minute) or contact support about the application.

Protect application is refused: hostname already protected

That hostname belongs to another application, possibly in another account. Remove it there first.

The public hostname and the origin must differ

Netway has to be able to reach your server under a name that is not the one it protects. Give the origin its own name, such as origin.example.com, or use its IPv4 address.

I removed protection and the site is down

The CNAME still points at Netway. Point the hostname back at your server. Next time, update DNS first and remove protection afterwards.

Attackers still reach my server directly

They found the origin. Change the origin hostname or address, update the application, and restrict the origin to accept traffic from Netway only.

Still stuck?

Open a ticket with your account ID, the application's hostname and what the DNS & TLS tab shows.

Contact support
Was this page helpful?
Updated 25 October 2026 Suggest an edit

Choose which cookies Ordnary may use. You can change this at any time via Cookie settings at the bottom of every page.