-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App/users page not load (Edge) #215
Comments
Hello @infraoderco, Thank you for the bug report and the additional information. Here is the internal follow-up ticket: PB-34421. We were unable to reproduce the error using the same version of Edge and the latest API, and we did not encounter any issues. Could you please confirm if the application is stuck in loading mode, as shown in the following screenshot: Could you check the result of the users.json request to see if the data returned by the API includes users with their profiles, such as:
The network activity can be viewed in the browser extension debug:
|
Yes, the page stuck just like that. I'm sorry, but I don't know so much the procedures, could you please explain where do I found the header like you said? When I check edge://extensions I didn't find the same information, I am noob with this. Thanks a lot for quick response |
Hello @infraoderco, Don't worry I will try to be clearer.
To do so click on the index.html link displayed in the "inspect views" section of the passbolt extension. |
Since we have not received further information and are unable to reproduce the issue, we are closing this bug report for now. If you encounter the issue again or have additional details, please feel free to reopen the report, and we will be happy to investigate further. |
ISSUE NAME
-- Browser: Edge 127.0.2651.98
-- Web server: PHP version 8.2.20
-- etc.: Server 4.9.1 Client 4.9.1
What you did
I no longer think the problem is related to some incorrect configuration on our part, but rather some problem related to the browser extension. What I did was the following: We have a dedicated Passbolt server internally, but we decided to create another server in the cloud for better remote access and we started using it while the internal Passbolt was on standby. At the time, the user screen still worked normally, even on the cloud server, but it was before the last update of the extension. After this update to version 4.9.1 of the extension, after a while we noticed this problem of not opening the user screen and we started investigating if we had made some incorrect configuration.
Since I didn’t find anything, I decided as a last test to delete all the information and create a new server in Docker from scratch. After I created and added the first user, even without any information on the server, the same error occurred, the user screen didn’t open. So I decided to go back to using the internal server that was working, but when I did that, I saw that the same error also occurred. At that time, I was using Microsoft Edge along with the extension downloaded from the Edge extension store. However, on another computer that was still pointed to the internal server, the user screen was working normally, but in Google Chrome. So I tried doing the same on my machine and, to my surprise, it worked perfectly. So I believed that the problem was with the extension from the Edge store and decided to uninstall this extension from Microsoft Edge and download the extension from the Google Chrome store on Edge, and voilà, it worked!
So with that in mind, I went back to pointing my computer to Passbolt in the cloud and did the same procedures as before. Unfortunately, in this case, it still didn’t work. It’s still the same. So, since the server was created from scratch, without any information, and yet the same thing happens, I can only believe that the problem is really something with the Extension, since it has nothing to do with the server itself.
What happened
The User's page not load
What you expected to happen
To access the user and groups page
The text was updated successfully, but these errors were encountered: