Connection Issues

Page loads but real-time features do not work

Vulnotes uses WebSocket connections (Socket.IO) for real-time collaboration, notifications, and presence indicators. If the page loads but you do not see other users' cursors or get notifications:

• Check that your reverse proxy is configured to pass WebSocket connections. Nginx needs proxy_set_header Upgrade $http_upgrade and proxy_set_header Connection "upgrade" directives.
• Corporate firewalls sometimes block WebSocket traffic. Try accessing from a different network to confirm.
• Check the browser console (F12) for WebSocket connection errors.

Cannot reach the Vulnotes instance

If the page does not load at all:

• On a connected on-premise deployment, run docker compose ps from its installation directory and inspect vulnotes logs
• Check that the configured port is not blocked by a firewall
• If behind a reverse proxy, verify the proxy is running and forwarding to the correct port
• For SaaS instances, check the instance status in Vulnotes Manager or contact support

CORS errors in browser console

If you see CORS errors, check that the public domain configured for the deployment matches the URL in your browser, including the protocol and port. A reverse proxy must forward the original host and protocol correctly. Check the generated configuration and backend logs before changing environment variables.

SSL certificate errors

If you get certificate warnings when accessing your on-premise instance:

• Make sure your SSL certificate is valid and not expired
• If using a self-signed certificate, add it to your browser's trusted certificates
• Check that the certificate covers the exact hostname you use