This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Newest update caused glitch with ShipStation

  • 2 replies
  • 0 have this problem
  • 6 views
  • Last reply by James

MartyleeCzajkowski
MartyleeCzajkowski
more options

I noticed that Firefox implemented an update today at 10:36 (CST). I have noticed that since that point I can no longer click the login button for my ShipStation platform. I can login without issue through Chrome, but prefer to use Firefox. I have cleared my history for ShipStation in Firefox. I have restarted my computer. The page loads, but clicking on the login button has not result - nothing happens.

Please help!

I noticed that Firefox implemented an update today at 10:36 (CST). I have noticed that since that point I can no longer click the login button for my ShipStation platform. I can login without issue through Chrome, but prefer to use Firefox. I have cleared my history for ShipStation in Firefox. I have restarted my computer. The page loads, but clicking on the login button has not result - nothing happens. Please help!

All Replies (2)

zeroknight
zeroknight
more options

The site use Google's reCAPTCHA technology which appears to be having technical difficulties in some regions currently. Try changing the user agent with User-Agent Switcher to make the browser look like Chrome.

James
James
  • Moderator
  • Top 10 Contributor
more options

It appears that Google has fixed this recaptcha issue for Windows Firefox users. You can change Firefox useragent back to the default if you did the temporary workaround by changing it with a useragant extension or by preference in about:config