Troubleshooting setup
When the wizard or the verify step has not yet seen your first event, it names the cause and the next step – never a generic error.
Ships with the first release
One command checks that a real event from your app has arrived and, if not, names what is missing and the next step.
These are the problems it recognises.
The ingestion key was refused
Section titled “The ingestion key was refused”The key is wrong, or it was switched off. Setting up again replaces the key in your env file.
Ships with the first release
One command finds your framework, signs you in from your browser, installs Xovris, writes your settings and waits until a real event from your app arrives – nothing to copy or paste.
Events are blocked before they leave your machine
Section titled “Events are blocked before they leave your machine”The ingest address did not resolve, the connection was refused or timed out, or the secure connection failed. Allow outbound HTTPS to the ingest address in your firewall or proxy.
Ships with the first release
One command checks that a real event from your app has arrived and, if not, names what is missing and the next step.
A browser extension blocked browser events
Section titled “A browser extension blocked browser events”An ad blocker stopped the request to the ingest address. Server events still arrive; browser events need to be sent through your own domain.
Your framework version is outside the supported range
Section titled “Your framework version is outside the supported range”The wizard stops before changing anything and names the range its changes are written for. Upgrade the framework to a version in that range and run it again. Each stack’s range is on its own page under Connect your app.
Your Node.js version is older than the SDK needs
Section titled “Your Node.js version is older than the SDK needs”The diagnosis names the supported range. Upgrade Node.js to a version in that range and run the wizard again.
Stack traces stay minified
Section titled “Stack traces stay minified”Your production build ran without the source-map upload token. Run the wizard again in the project to add the build token to your platform.