When trying to run flowdock on chrome or chromium it doesn't load at all. It works on firefox though. I get this loop of 404 and reconnecting. Can you do something about it?
We are looking into this issue. We have a couple of reports from other users that reloading the Flowdock App (Cmd +R on a Mac) or trying to access Flowdock via a new Private browser session or from a different browser has worked for them.
We'll keep you updated on the progress and you can also check our status page at http://status.flowdock.com/.
I apologize for the inconvenience this issue has caused for you and your team.
Michael Bulkeley CA Flowdock Customer Support
Is it possible for you to expand your view of the Developer Tools so we can see the entire URL that is experiencing the 404?
Here you go.
I'm having the same problem here. The URL that 404s is
This has been going on since about yesterday. As a side note, I e-mailed firstname.lastname@example.org, hoping I could get some support there, but that doesn't seem to have happened. Is this forum the only official support channel for paying customers?
One of my colleagues is having a similar issue, other colleagues say it's ok for them. Perhaps it depends on geographical location (something wrong with a CDN perhaps)? I work remote from France. Using Firefox 56.0 on Ubuntu 16.04.
It would be nice to get a fix soon, as Flowdock is essential for communicating with my team.
And here is the same error with curl :
$ curl -vv "https://www.flowdock.com/jplex/?EIO=3&transport=polling&t=1510577097816-1"* Trying 18.104.22.168...* Connected to www.flowdock.com (22.214.171.124) port 443 (#0)* found 148 certificates in /etc/ssl/certs/ca-certificates.crt* found 604 certificates in /etc/ssl/certs* ALPN, offering http/1.1* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256* server certificate verification OK* server certificate status verification SKIPPED* common name: *.flowdock.com (matched)* server certificate expiration date OK* server certificate activation date OK* certificate public key: RSA* certificate version: #3* subject: OU=Domain Control Validated,OU=PositiveSSL Wildcard,CN=*.flowdock.com* start date: Wed, 27 Nov 2013 00:00:00 GMT* expire date: Mon, 26 Nov 2018 23:59:59 GMT* issuer: C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO RSA Domain Validation Secure Server CA* compression: NULL* ALPN, server did not agree to a protocol> GET /jplex/?EIO=3&transport=polling&t=1510577097816-1 HTTP/1.1> Host: www.flowdock.com> User-Agent: curl/7.47.0> Accept: */*> < HTTP/1.1 404 Not Found< X-Powered-By: Express< Content-Security-Policy: default-src 'self'< X-Content-Type-Options: nosniff< Content-Type: text/html; charset=utf-8< Content-Length: 149< Date: Mon, 13 Nov 2017 12:49:17 GMT< Set-Cookie: FD_WEBSOCKET_ID=jplex1s3|WgmU0|WgmU0; path=/; HttpOnly; Secure< Connection: close< <!DOCTYPE html><html lang="en"><head><meta charset="utf-8"><title>Error</title></head><body><pre>Cannot GET /socket.io/</pre></body></html>* Closing connection 0
Quick fix: seems I like I can workaround the issue by adding the line
to my /etc/hosts file.
The Operations Team has made a change. Would you and your users try accessing Flowdock again and let us know if there is any difference now?
If there is still an issue, can you provide a screen shot of the Network Tab from the Developers Toolbar? To access this in Chrome, you click on the three vertical dots in the upper right corner and select More Tools > Developer Tools. We are specifically looking to see if the 404 errors are coming from an address similar to:
No, it still doesn't work (unless I make the workaround mentioned above in /etc/hosts ). The 404 errors are still coming from the following URL:
There has been another update made, is it working for you and your team now?
It seems to work now indeed. Thank you!
Still an issue.
Does it make any difference if you login via a new InPrivate or Icognito browsing session?
It doesn't make any difference from my point of view.
Thank you, can you try once more, another update was made by the Operations Team.
Well.. it worked like a charm. Thank you.
Thank you, I am glad that it is sorted for you and your team.
I apologize again for the inconvenience this issue has caused.
Please let us know if you have any other issues or questions.
Retrieving data ...