Closed Bug 1873169 Opened 1 year ago Closed 1 year ago

Gmail setup fails when running a webserver on localhost

Categories

(Thunderbird :: Untriaged, defect)

Thunderbird 115
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1748416

People

(Reporter: kljbonnema, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:121.0) Gecko/20100101 Firefox/121.0

Steps to reproduce:

Add new mail account for a gmail address. Thunderbird finds the proper gmail configuration details. When you accept the configuration you have to present your Google account login details and finally accept that you give Thunderbird access to your mail. From here the account should be finalized and mails should be received.

Actual results:

After accepting that Thunderbird has access to you gmail Thunderbird displays a message that connection failed, probably due to invalid configuration or account details.
What really happened is that after accepting the access to gmail, the Thunderbird internal browser is directed to localhost (port 443, 80, 8080,...). If you are running a webserver or other service listening to these ports then the redirect will be consumed by the webserer. This causes the account setup to fail.
As a workaround you can temporarily turn off the webserver during the setup process and start it again after the setup completed.
However - there is no indication at all why the setup goes wrong and a user may be completely stumped by it.

Expected results:

Thunderbird should be prepared to accept that there is a localhost process listening to ports 80, 443 and act accordingly to mitigate and continue with the setup process.

If it is impossible to continue with the gmail account setup while a localhost process is active on ports 80, 443 then Thunderbird should show a message reporting this suggesting to temporarilly turn of the localhost process.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Duplicate of bug: 1748416
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.