-
Notifications
You must be signed in to change notification settings - Fork 183
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
get illegal token error #210
Comments
@hajika ouch, this sounds bad. Can you give me a bit more details? When is that you get that? On starting jingo, on loading the first page or somewhere else? thanks! |
I get this on opening any page. I checked the
It might be because of the |
Thanks, but this is still not enough: can you please send me also your config.yaml? What is your server (or workstation) configuration? Windows maybe? |
CentOs 6 As I said, I completely reinstalled the whole thing, in the config.yaml I only changed the port and the repository path, anything else is like in the default. I also initiated a new git repo. |
So I still encounter that problem with the master branch, but not with the v1.7.3, so I hope this will vanish with the next release :) |
It must have something to do with the 1.8.0 release, then (there were big changes there), but I cannot reproduce it on OSX and Ubuntu at the moment. One of the templates is probably broken somehow but I can't understand where the problem is. |
In the meanwhile try the current version (1.8.1) |
Can you also please tell me you node js version? |
I just tried the v1.8.2 and the error appears again. Node version is v0.12.9, but I can change I easily if there is any benefit in it.. |
I am pretty sure Node 0.x is not supported anymore, or not supported very well at least. Please use any of the LTS (since you are updating, go for 6.x) Thanks |
I suddenly get this error when opening jingo:
I already completely reinstalled jingo and created a new repo, but the error is still there. I cant imagine why?! As far as I know, that can happen when there is an invisible character in JS code, but how suddenly and why its not working after reinstallation?
The text was updated successfully, but these errors were encountered: