WEBDANGER / DOCS / OPERATE

Troubleshooting

Find the next action without losing your work.

01

The page did not change

Check the selected project, published version and public address. A local preview and a public deployment can show different versions. Inspect deployment status before publishing again.

  1. Compare the selected deployment with the public URL.
  2. Check status before repeating upload or publication.
02

DangerCode did not open

Use the product switch in Consol and choose a project. If no projects exist, create one in Sites. The original embedded interface remains in development; a disconnected engine is shown explicitly.

  1. Select a project and inspect the displayed connection state.
  2. Preserve the task reference and describe the last confirmed step if execution was interrupted.
03

Ask support

Open support in Consol and include the project name, public URL, time of the error and a screenshot with private data removed. Do not send passwords, provider keys or CLI tokens.

  1. Send support the project name, public URL and time of the error.
  2. Include a redacted screenshot; omit passwords, private keys and CLI tokens.

WEBDANGER support.

Get help with your account, website, domain, billing or CARE offer.

contact@webdanger.com

The reply appears in this conversation. Email remains a fallback identity.