Install your On-premise version of Bugsnag on a machine without an internet connection.
If you have the Clustered version of Bugsnag On-premise, please follow the clustered installation guide instead.
To get started with your Bugsnag On-premise installation, you’ll need the following things prepared in advance:
If you are installing Bugsnag On-premise on an internet connected machine please follow the online installation guide.
Bugsnag On-premise uses Replicated to perform and manage installations. To install Bugsnag On-premise we first need to install and configure Replicated.
Download the latest replicated release:
curl -sSL -o replicated.tar.gz https://s3.amazonaws.com/replicated-airgap-work/replicated.tar.gz
Bugsnag will have provided you with a URL to download the offline installation package. You should download this and ensure the filename ends in
curl -sSL -o bugsnag.airgap "<URL provided>"
Now copy the
replicated.tar.gz file and the
.airgap file to the destination server, ready for the installation. Also copy the
.rli license file provided by Bugsnag over to the destination server.
Now on the destination machine, run through the replicated installation procedure:
tar xzvf replicated.tar.gz cat ./install.sh | sudo bash -s airgap no-auto
The installation script will attempt to automatically detect the private IP address of the machine. If the script is unable to detect the machine’s IP address it will present you a list of network interfaces to choose from, select the one has the machine’s IP address on your network. Typically this will be the
After installation, the Replicated management console will be available at
Upon first visiting the Replicated management console you will be asked to set a hostname and certificate for the management console. Doing so will remove the SSL certificate warning when accessing the management console, but you can continue with the self-signed certificate and update this later if you prefer.
.rli license file you received from Bugsnag and select the Airgapped installation method to continue.
Now provide the full path to the
Once the license has been uploaded and validated, you should set a password for the management console - this is particularly important if you are exposing it to a public network and will be required to access the management console again in the future.
You will then be presented with the preflight check page, this will analyze the system to determine if the environment meets the minimum requirements. These checks are done to ensure that your installation is successful, and although you can skip these checks and force an installation, we recommend you consult with us before doing so.
Finally, configure your installation as directed on the settings page, save and start Bugsnag.
In the console settings page, there is a section to set the Airgap mode settings. You can install updates by downloading a new version of the .airgap package and placing it in the location specified on the console settings page. You will need to sync the license when we send you a new version of it, replacing it at the location specified.
It can take several minutes for Bugsnag On-premise to fully start up; when it is ready the management console will indicate that it is
Now Bugsnag is running, you should be able to access the Bugsnag dashboard, where you’ll need to create your account and first project.
Visit your Bugsnag dashboard in a web browser (available by default at x.x.x.x:49080) to set up your account and create projects for each of the applications you wish to monitor.
Once you have created your account and first project you will need to configure your applications to send errors and sessions information to your Bugsnag instance instead of notify.bugsnag.com and sessions.bugsnag.com respectively. Follow the instructions on configuring platform notifiers for how to do this.