ProtonMail / proton-bridge

Proton Mail Bridge application
GNU General Public License v3.0
1.14k stars 155 forks source link

Upon start i get a gRPC server error #345

Closed rottenpants466 closed 1 year ago

rottenpants466 commented 1 year ago

Hi,

I recently performed a clean installation of Windows 11 and then i proceeded to install the latest version of Proton Bridge. The app doesn't open and it shows 2 similar errors.

Expected Behavior

Proton Bridge should start normaly.

Current Behavior

When starting the app it shows one of these errors depending on if i start with Administration Rights:

Cannot connectToServer to go backend via gRPC: Server failed to generate certificate on time.

or

Bridge application exited before providing a gRPC service configuration file.

Possible Solution

I have no idea. Tried to reinstall Bridge again but i get the same error.

Version Information

Windows 11 Pro 22H2 with latest updates Proton Bridge v3.0.18

gabor-meszaros commented 1 year ago

Hi @rottenpants466, Thank you for reporting this issue. We do not have many gRPC related errors reported to us, so your logs would be very useful. Can you please contact Proton customer support and send your logs to us? You can use the built in report function, or just zip all the log files you have and report it through web. Thank you!

rottenpants466 commented 1 year ago

Hi @rottenpants466, Thank you for reporting this issue. We do not have many gRPC related errors reported to us, so your logs would be very useful. Can you please contact Proton customer support and send your logs to us? You can use the built in report function, or just zip all the log files you have and report it through web. Thank you!

Thanks for responding!

Sorry to ask but can you tell me where the logs are located?

Thank you!

gabor-meszaros commented 1 year ago

On Windows, it should be under C:\Users\username\AppData\Roaming\protonmail\bridge-v3\logs.

gabor-meszaros commented 1 year ago

@rottenpants466 I am sorry, I shared a wrong path before. Now I updated it to the correct one.

rottenpants466 commented 1 year ago

Thank you!

rottenpants466 commented 1 year ago

Don't know why but bridge creates 2 more users for some reason, is this normal?

Captura de ecrã 2023-02-25 000016

v3.0.18_82c388a0dd_1677282985.log

v3.0.18_82c388a0dd_1677282984.log

Edit:

One of the strange user folders (first one) also has a log:

gui_v3.0.18_1677282984.log

rottenpants466 commented 1 year ago

Tried other v3 versions same thing happens.

andrzejsza commented 1 year ago

Thanks for this report - the extra users' folder is clearly a bug. After investigation, it turned out that this is due to the path of the user home folder containing accents. Potentially, this is also the reason for the original problem, as bridge-gui would struggle to retrieve the user config, data, and cache folder. We should have a hotfix in the coming days, will post it here.

rottenpants466 commented 1 year ago

Thank you!

Should i close this issue?

andrzejsza commented 1 year ago

let's wait for the fix to be out 👌

Babak-mhy commented 1 year ago

I've got the exact same issue as well!

andrzejsza commented 1 year ago

would you mind confirming with the current beta 3.0.19? might be best to first uninstall the current version completely and delete those weird looking user folders...

rottenpants466 commented 1 year ago

I can report the problem was fixed in 3.0.19 beta 👍

Proton Bridge starts up normaly and i was able to login. Also no more weird user folders 👍

Thank you!

andrzejsza commented 1 year ago

glad to hear. closing.

Zachiah commented 9 months ago

I'm getting the

Bridge application exited before providing a gRPC service configuration file.

on MacOS ever since I setup Nix. Any idea why?

EDIT To be clear, I'm not running Bridge through Nix, it's just that I installed nix and it is no longer working. I have tried reinstalling Bridge as well

LBeernaertProton commented 9 months ago

We usually see this error if there is an issue interacting with the macOS keychain.

Zachiah commented 9 months ago

We usually see this error if there is an issue interacting with the macOS keychain.

Thanks for your reply! Do you have any recommendations on first steps to debug this?