Error connecting the browser extension to MySafe
- 2 minutes to read
- Print
- DarkLight
- PDF
Error connecting the browser extension to MySafe
- 2 minutes to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
This document provides guidance on resolving common issues when trying to connect the browser extension to MySafe. Each issue is described with an error message, possible causes, and recommended solutions. Follow the step-by-step instructions to troubleshoot the problem.
Problem overview
| Problem | Error message | Main cause | Solution |
|---|---|---|---|
| Problem 1 | “It’s not possible to reach your senhasegura instance, please make sure you’re connected to internet and have access to your senhasegura instance.” | No connection to the senhasegura server. Incorrect configuration of the base URL in MySafe. Self-signed certificate on the senhasegura server. | Solution 1 Solution 2 Solution 3 |
| Problem 2 | “An unexpected error occurred, please try again in a few moments or contact our support team.” | Incorrect URL configured in Orbit Server Manager. | Solution 4 |
| Problem 3 | “Invalid code” | Application incorrectly created as mobile app type. | Solution 5 |
Solutions
Solution 1: Verify connection to senhasegura
Ensure that the device has a stable connection to the senhasegura server.
Step completion: after checking the connection stability, try connecting the extension to MySafe again. If the error persists, proceed to the next solution.
Solution 2: Review system settings
- Prerequisites: senhasegura instance administrator permission.
Attention
Ask the administrator to check system settings and your access permissions.
In the Products menu, go to MySafe > Global administration > Sharing options.
- Enter an email for notifications related to MySafe.
- In Base URL, enter the MySafe vault URL without the
https://.
Example:company.mt4.com
InfoThe other fields on this screen are related to the External sharing feature, available only for the web version. More information in How to configure MySafe.
Step completion: after configuring the base URL, try connecting the browser extension to MySafe again. If the error persists, proceed to the next solution.
Solution 3: Configure the browser for self-signed certificates
- If the senhasegura server is using a self-signed certificate, close the browser and launch it with the
--ignore-certificate-errorsflag. For example, if you’re using Google Chrome, launch the browser withchrome.exe --ignore-certificate-errors.
Step completion: after restarting the browser with the correct configuration, try connecting the browser extension to MySafe again. If the error persists, proceed to the next solution.
Solution 4: Check settings in Orbit Server Manager
- Prerequisites: senhasegura instance administrator permission.
Attention
Ask the administrator to check the Orbit Server Manager settings.
- In Orbit Server Manager, go to Settings > Application.
- Check if the application URL is configured correctly.
- If necessary, click Edit in the upper-right corner and adjust the URL.
Step completion: after correcting the application URL, try connecting the browser extension to MySafe again. If the error persists, proceed to the next solution.
Solution 5: Check the created application type
- In MySafe > Mys apps, click Add.
- In Application type*, select Extension.
- Click Save.
Step completion: after checking and correcting the application type, try connecting the browser extension to MySafe again.
If the error persists after following the instructions, contact technical support for further assistance.
Was this article helpful?
