Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多
封存

access denied to lobstr.co

pezzeipeter

'since the update from Aug 20 to 129.02 cannot open lobstr.co on firefox (after 8 captchas get error). Have no problem opening lobstr on Windows or Google. So this has to do with your last update. What do you suggest?

                                                                                                       Best regards
                                                                                                             Peter
'since the update from Aug 20 to 129.02 cannot open lobstr.co on firefox (after 8 captchas get error). Have no problem opening lobstr on Windows or Google. So this has to do with your last update. What do you suggest? Best regards Peter

所有回覆 (3)

I suggest you show us what you're getting when you try the site. Here is what I see. see screenshot

Which screenshot? For opening lobstr.co you have to give in your e-mail-address and your password. Then you get a link into your e-mail to open again, give in the PW again. Normally you would have to give-in the 2 FA- 6-digit code then. But actually there is always Captchas. Even you fill them out correctly you are denied access. Maybe it`s not synchronized anymore. But the problem exists only since a few days(= the last update).

                                                                                                                 Best regards
                                                                                                                      Peter

Which screenshot? For opening lobstr.co you have to give in your e-mail-address and your password. Then you get a link into your e-mail to open again, give in the PW again. Normally you would have to give-in the 2 FA- 6-digit code then. But actually there is always Captchas. Even you fill them out correctly you are denied access. Maybe it`s not synchronized anymore. But the problem exists only since a few days(= the last update).

                                                                                                                  Best regards
                                                                                                                        Peter