Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Learn More

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

what's the relevant timeout for this really slow connection?

  • 4 відповіді
  • 1 має цю проблему
  • 3 перегляди
  • Остання відповідь від RandomTroll

more options

When I try to connect to https://mim.t-mobile.com/primary/openPage Firefox returns, 'The connection has timed out

The server at mim.t-mobile.com is taking too long to respond.' Opera & Lynx don't connect either. I can connect at a public computer, but the connection can take minutes to make, and sometimes it gives up. (They're Windoze; I'm Linux.) What's the relevant timeout to see if I really could connect if I gave Firefox minutes to try?

When I try to connect to https://mim.t-mobile.com/primary/openPage Firefox returns, 'The connection has timed out The server at mim.t-mobile.com is taking too long to respond.' Opera & Lynx don't connect either. I can connect at a public computer, but the connection can take minutes to make, and sometimes it gives up. (They're Windoze; I'm Linux.) What's the relevant timeout to see if I really could connect if I gave Firefox minutes to try?

Усі відповіді (4)

more options

Please check this question and answer it helps you to adjust the timout setting

https://support.mozilla.org/en-US/questions/1042479

more options

These instructions are obsolete. I found another thread on timeouts that was also obsolete before I asked.

more options

Hi,

The solution is to clear the caches and the history. I share the link that will give you all the information to stop seeing this message


https://support.mozilla.org/en-US/kb/websites-dont-load-troubleshoot-and-fix-errors


Thank's

more options

hellosct1 said

The solution is to clear the caches and the history.

No, it isn't. This behavior started in March. I've tried all of that multiple times. I don't even keep a history.