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

Run JSBin Locally - unable to save #2242

Closed
emnh opened this issue Jan 25, 2015 · 7 comments
Closed

Run JSBin Locally - unable to save #2242

emnh opened this issue Jan 25, 2015 · 7 comments
Labels

Comments

@emnh
Copy link
Contributor

emnh commented Jan 25, 2015

When I edit the HTML or JS I get the following red error message at the top:

"I think there's something wrong with your session and I'm unable to save. Refresh to fix this, you will not lose your code." Clicking refresh doesn't help.

JS console shows "POST http://192.168.100.128:3000/save 403 (Forbidden)".

Server log, same, forbidden:
192.168.100.1 - - [Sun, 25 Jan 2015 00:59:43 GMT] "POST /save HTTP/1.1" 403 2982 "http://192.168.100.128:3000/?html,js,output" "Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.99 Safari/537.36"

@emnh
Copy link
Contributor Author

emnh commented Jan 25, 2015

Setting the session secret didn't help.

Production or development doesn't make a difference.

Setting logger to "dev" in config.local.json didn't give any more output.

Fixing timezone didn't help.

Any tips for how to debug it?

@emnh
Copy link
Contributor Author

emnh commented Jan 25, 2015

Found the error in the request response:

403 Forbidden:

Forbidden

403 Forbidden:

Forbidden
at Object.exports.create (/home/emh/dev/jsbin/lib/errors.js:103:12)
at ErrorHandler.module.exports.Observable.extend.coerceError (/home/emh/dev/jsbin/lib/handlers/error.js:156:21)
at ErrorHandler.module.exports.Observable.extend.httpError (/home/emh/dev/jsbin/lib/handlers/error.js:25:16)
at next (/home/emh/dev/jsbin/node_modules/express/node_modules/connect/lib/proto.js:194:17)
at next (/home/emh/dev/jsbin/node_modules/express/node_modules/connect/lib/proto.js:196:11)
at module.exports.Observable.extend.githubCallbackWithError (/home/emh/dev/jsbin/lib/handlers/session.js:607:5)
at next (/home/emh/dev/jsbin/node_modules/express/node_modules/connect/lib/proto.js:194:17)
at next (/home/emh/dev/jsbin/node_modules/express/node_modules/connect/lib/proto.js:196:11)
at next (/home/emh/dev/jsbin/node_modules/express/node_modules/connect/lib/proto.js:196:11)
at next (/home/emh/dev/jsbin/node_modules/express/node_modules/connect/lib/proto.js:196:11)

@emnh
Copy link
Contributor Author

emnh commented Jan 25, 2015

It works in IE 10 and Firefox 35.0 but not in Chrome 40.0.2214.91.

In the POST data, checksum is false in Chrome while it looks like a checksum in IE and FireFox.

Does the folder "public/js/chrome" in the source code have something to do with Chrome browser? Are there specific code paths for Chrome?

@emnh
Copy link
Contributor Author

emnh commented Jan 28, 2015

Tried it on a public facing web host and there it worked, also in Chrome.
Other than that, node binaries were 32-bit on this working server, only other difference I know.

@baixiaoji
Copy link

so answer is needing on a public facing web host ? today, I having the same error in Chrome 59.0.3071.104, and I am on a public facing web host, even though I having some doubts about meaning of the 'public facing web host '?

@emnh
Copy link
Contributor Author

emnh commented Jun 16, 2017

I don't remember much about this, but I think the JSBin site had to be accessed through a public domain name (or maybe public IP address was enough?). Sorry, I don't remember.

@stale
Copy link

stale bot commented Jan 19, 2018

This issue has been automatically marked as stale because it has not had recent activity. More importantly, jsbin has been undergoing a massive refactor by Remy, and a large number of issues have been resolved, but with the growing 600+ open issues, the Stalebot (me), has been brought in to try to manage the issues.
Keep an eye on jsbin.com blog posts and the @js_bin twitter account for updates on the new version of jsbin ❤️
It will be closed next week if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jan 19, 2018
@stale stale bot closed this as completed Jan 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants