Search Documentation
-
Deployment
-
Administrative Guide
- Settings
- Sharing Files
- Authentication Mechanisms
- Audit
- Backup & Restore
- Search Files using Index Service
- SSO Configuration For AdminConsole
- Admin Roles
- Access Restriction with IP Address
- System Requirements
-
- 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
-
- Articles coming soon
-
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
How to Restart Services
NirvaShare is bundled with the below services and these services can be restarted in one go.
- Admin Console
- User application
- Index service
- Database
You will require access to your machine where NirvaShare is installed. To login, ssh to the Linux machine as root user or with a user having access to docker containers.
Run the below command to restart all the above services.
sudo root
docker-compose -f /var/nirvashare/install-app.yml restart