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
Isso isn't showing up on my blog anymore #667
Comments
I would say you are using too current a version of werkzeug (#617). Have you made an appropriate update lately? |
Hello, Thank you. I used pip3 to install not pip:
|
Try checking your browser console for Javascript errors. If you find it's missing 'embed.min.js', see #656 (comment) |
Yeah I got a 404 error. Trying your version:
|
If I run:
I see |
I see it, Bower (1.8.8) and NPM (6.14.6) are installed I saw no errors while building again. Where can I find the logs? I have embed.min.js in my |
I suggest starting from scratch in a new venv:
So not
Then in your systemd service script, make sure you use the absolute path to the correct
( When a new isso release is made fixing #617, you can move off An example: for my own site, I have isso installed in a venv just as in my last comment. I then have a systemd unit starting isso after the website (
|
I really thought this solution might work, but it did not :/ Due to the steps above not working. Isso wasn't building in the directory.
My steps in /home/isso. I have the /home/isso/venv/lib/python3.6/site-packages/isso/js/embed.min.js file. Running
/home/isso/venv/lib/python3.6/site-packages/isso/js/embed.min.js My systemd service
|
What do you mean by not building? Is it throwing errors when you If
If that works (doesn't immediately exit with an error), then open another terminal and check if the web interface works by visiting the URL given in the
If isso appears to start but you can't access its admin port (via If isso's admin UI works, ctrl-c your command-line isso, If all that works, then isso is mostly working. Check your isso |
My apologies, I was referring to something else. I should have made it more clear. isso@cbtree:~$ telnet localhost 4590
$ links -dump http://localhost:4590
$ links -dump http://localhost:4590/admin
It's enabled true, under moderation. cranberrypie@cbtree:~$ sudo -u isso /home/isso/venv/bin/isso -c /home/isso/isso.conf run It basically doesn't output anything else, it freezes. I do have an admin password as seen in my config in the OP.
log file = isso.log
|
The relevant line there is:
Do a (That |
I tried to use the Just showing you the output below. $ ps axwu | grep isso --- running
Stopped.
Had to adjust the config: $ links -dump http://localhost:4590/admin
When going to http://localhost:4590 without /admin it gives;
I still don't see it on my blog. EDIT I don't think it's my Nginx? Was working before. -- /etc/nginx/sites-available/domain.com.conf
|
Since
|
Well I want to say, thanks for your help thus far. I truly do appreciate it. What I don't understand is Isso was working and then just stopped. From all the information below, nothing seems to be a related error. Running both:
The snippet in my blog
Nginx error.log / error.log.1 error.log
error.log.1
Nginx access.log
Isso.log (same error as above which you told me was a false error)
Only console error on firefox browser is |
To to clarify, Your Ghost snippet indicates isso should be listening on |
Both my .conf and ssl.conf for my isso subdomain worked before. Otherwise the localhost url seems to work. $ links -dump http://localhost:4590/admin
My isso.domain.com.conf
My isso.domain.com-ssl.conf
|
Well, you've got a working http://localhost:4590/admin, so nginx must be the problem. Why do you have only |
That worked, I removed /comments. The weird thing is this wasn't an issue before, it worked before. I never touched anything after I setup Isso the first time, so genuinely curious how it came to stop working altogether. Thanks for your help. Comments work now. Although I do get a URL not found error when going to isso.mydomain.com/comments/admin or just /comments and /admin.
|
Glad it's working! I wouldn't expect As for nginx, it looks like at one point you might have wanted isso on
If it's all happy (should check the comment approval process) please mark this issue as resolved. |
For users having issues accessing the admin panel due to Nginx configuration. Try this:
|
The service appears to be running, but it appears Isso decided to quit.
$ sudo systemctl status isso
My config:
The text was updated successfully, but these errors were encountered: