Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Gmail OAuth login "script terminated by timeout"

  • 1 reply
  • 0 have this problem
  • 2 views
  • Last reply by Adrian Lee

more options

I reinstalled thunderbird and cleared the profile folder. Then when I login Gmail, after the OAuth, it tells me "Unable to login at server. Possibly wrong configuration, username or password."

This only happens to Gmail. I also tried Outlook and this didn't happen.

I then tried running thunderbird in the terminal to see what it outputs: (image 2)

"line 232: Script terminated by timeout"

Technical information: TB version: 128.5.1-1 (arch linux aur)

I reinstalled thunderbird and cleared the profile folder. Then when I login Gmail, after the OAuth, it tells me "Unable to login at server. Possibly wrong configuration, username or password." This only happens to Gmail. I also tried Outlook and this didn't happen. I then tried running thunderbird in the terminal to see what it outputs: (image 2) "line 232: Script terminated by timeout" Technical information: TB version: 128.5.1-1 (arch linux aur)
Attached screenshots

Chosen solution

tl;dr: check if anything is using port 8080 then stop that process

I also confirmed that my firewall is not interfering with the login process.

However, it turns out thunderbird requires a certain port (i suspect 8080) to be open and I have a few podman containers running on the same machine that interfered with the port thunderbird is using. After stopping all the podman containers I am able to login normally.

Read this answer in context 👍 0

All Replies (1)

more options

Chosen Solution

tl;dr: check if anything is using port 8080 then stop that process

I also confirmed that my firewall is not interfering with the login process.

However, it turns out thunderbird requires a certain port (i suspect 8080) to be open and I have a few podman containers running on the same machine that interfered with the port thunderbird is using. After stopping all the podman containers I am able to login normally.

Modified by Adrian Lee

Helpful?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.