Search Documentation
-
Deployment
-
Administrative Guide
-
- AWS S3 Storage Configuration using Access and Secret keys
- AWS S3 Storage Configuration using IAM role
- Google Storage Configuration using JSON Authentication Key
- Azure Blob/File Storage Configuration using Access Keys
- Backblaze B2 Storage Configuration using Access and Secret Keys
- DigitalOcean Storage Configuration using Access and Secret Keys
- Oracle Storage Configuration using Access and Secret Keys
- Wasabi Storage Configuration
-
-
Tutorials
- Quick Start
- AWS S3 File Sharing With Password Protection
- Google Cloud Storage Integration
- SSO for Admin Console using IAM Identity Center
- SSL and Load balancer for NirvaShare on AWS
- SSO for AdminConsole using Azure ActiveDirectory
- SSL Using Nginx Proxy Manager
- How to Share and Manage File Access from AWS S3, Azure Blob with Salesforce Users
- Configure SSO for Admin Console using Google Workspace as Identity Provider
- Share Azure Blob Files with ActiveDirectory Users using SSO
- S3 File Sharing with Okta Users
-
Troubleshoot
Table of Contents
< All Topics
User Application/File Server URL
NirvaShare is bundled with two applications, one for administrative console and other for user facing application. User application contains components for file sharing and authentication. Mention the domain name of user app here.
Here are the steps.
- Login to Admin Console and click on Settings from the left menu and then User Application/File Server URL
- Click on Edit, make the changes and save it

If you are testing without domain name, use the IP address of the user application or leave it blank. For example http://10.141.41.9:8081
For production deployment, it is recommended to use proper domain name with SSL.
This will be the base URL for the Share link that you create and share files with users.