Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(1.1.1) Blank UI at synctrayzor start, refresh browser / restarting syncthing fixes it. #201

Closed
Nihim opened this issue Jan 12, 2016 · 7 comments

Comments

@Nihim
Copy link

Nihim commented Jan 12, 2016

windows 7 64x portable 1.1.1

After I upgraded & started synctrayzor it showed no devices / folders and buttons were unresponsive. Clicking from the menu syncthing restart fixed it. As suggested in IRC, also refresh browser fixes.

Same behaviour happens every time synctrayzor is started.

If I choose open in external browser (firefox) it is unaffected.

Will try portable chrome as asked by canton7.

@canton7
Copy link
Owner

canton7 commented Jan 12, 2016

Error from go: tls: client using inappropriate protocol fallback. Error from JS: Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR.

Fails to load important JS files, and everything goes pear-shaped from there.

@canton7
Copy link
Owner

canton7 commented Jan 12, 2016

Suspecting an AV at this point - it's only the first few requests that fail, and only when cefsharp.browersubprocess.exe is newly started.

@Nihim
Copy link
Author

Nihim commented Jan 12, 2016

Stopping "active shields" or excluding the synctrayzor directory from any scans doesn't help. As canton7 said on the initial run of synctrayzor it works fine, afterwards TLS warning appears.

AV: Avast 11.1.2245 (2016?)

@Nihim
Copy link
Author

Nihim commented Jan 14, 2016

With 1.1.2 the problem is fixed? and UI is a lot snappier.
Initial run: fast and ok
Close and reopen window: fast and ok
restart synctrayzor and reopen window: fast and ok

Now if you didn't change something to do with the JS / TLS I have a theory though it's a bit ungrounded and far fetched so will tell you in IRC about it if you want to avoid public ridicule :P

@canton7
Copy link
Owner

canton7 commented Jan 14, 2016

Nothing's changed in that area since way back in 1.0-land. I'll bug you on IRC :)

@canton7
Copy link
Owner

canton7 commented Jan 22, 2016

Turns out to be related to how long the Computer's been running.

Not sure exactly what's causing it, but pretty sure it's nothing I can fix. Closing 😄

@canton7 canton7 closed this as completed Jan 22, 2016
canton7 added a commit that referenced this issue Jan 29, 2016
This means we'll end up with redirects on all requests if Syncthing is
forcing https, but I think that's OK.

Should help with #201.
@canton7
Copy link
Owner

canton7 commented Jan 29, 2016

For the next release I'm no longer forcing Syncthing to use https, which means it should default to http. That should work around this issue.

canton7 added a commit that referenced this issue Jan 29, 2016
This means we'll end up with redirects on all requests if Syncthing is
forcing https, but I think that's OK.

Should help with #201.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants