Skip to main content

Documentation Index

Fetch the complete documentation index at: https://learn.nexudus.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Rollback and Troubleshooting

If you encounter issues after migrating to version 5 of the Members Portal, you can revert to your previous version at any time. This page explains how to roll back and addresses common migration issues.

​
Rolling back to the previous version

To roll back to version 4, contact support@nexudus.com. The support team will revert your portal and confirm once the change is active. If you updated your DNS records as part of the migration, you will also need to revert them to point back to spaces.nexudus.com once the rollback is confirmed. This ensures your custom domain continues to resolve correctly with the previous version.
Rolling back does not affect your data. Bookings, invoices, customer accounts, and all other data remain intact regardless of which portal version is active.

​
Common issues

​
Custom CSS or JavaScript is not applied

Custom files (app.js, styles.css, head.js) must be opened and saved at least once in the Web Template Editor before they take effect in version 5. Solution: Go to Settings > Website > Web Template Editor > Built-in Files, open each file, and click Save. See Custom Code and Fonts for details.

​
CSS overrides from version 4 look wrong

Version 5 uses different class names and a new layout structure. CSS selectors targeting version 4 elements may no longer match. Solution: Review your styles.css file and update selectors to match the new portal markup. Use your browser’s developer tools to inspect the current elements. Old links that were distributed before the migration — in emails, bookmarks, or documents — are automatically redirected to the corresponding page on the new portal. If you are not using a custom domain, the old address (ending in .spaces.nexudus.com) also redirects automatically to the new one (ending in .nexudus.site). Solution: Redirects are handled automatically. If a specific link is not redirecting, clear your browser cache and try again. If the issue persists, contact support. While previewing the portal (before going live), email notifications continue to link to the current active version. After you go live, notification links update automatically. Solution: If links still point to the old portal after going live, clear your browser cache and wait a few minutes for the change to propagate.

​
Custom domain shows a certificate warning

After updating DNS records, SSL certificates need time to be issued and propagated. Solution: Verify that your DNS records match exactly what is shown in Settings > Website > Domain. Certificate generation typically completes within a few minutes once DNS records are verified, but DNS propagation itself can take up to 48 hours.

​
Customers cannot sign in

Customer credentials do not change during migration. If a customer reports sign-in issues, the cause is usually a cached version of the portal. Solution: Ask the customer to clear their browser cache, or try signing in using an incognito/private window.

​
Portal is slow to load after migration

The first load after migration may be slightly slower as the browser caches new assets. Solution: This is temporary and resolves after the initial load. If performance issues persist, check your custom JavaScript (app.js) for heavy operations that may conflict with the new portal.