New problem :), sorry I keep posting lots of issues.
So here is my configuration for my selfhosted forum goglides.dev. Feed url is valid.
Actuall...
For further actions, you may consider blocking this person and/or reporting abuse
@ellativity, I just figure it out answer to all my problem, which include stats update, mailchimp subscription, draft imports etc, I haven't include sidekiq cron jobs. I just ran this command manually from one of the forem container and started fixing the issue.
bundle exec sidekiq -c 2And this solved all your problems, @pandeybk? 🤯
yes all I posted here so far.
Thanks for asking these questions @pandeybk! I really appreciate the way you're splitting them into separate posts, as that makes it easier for people to find them in the search later on!
Just to confirm, you've checked your personal dashboard and your posts haven't imported there as drafts?
Yes, I did; in fact, the same RSS feed URL works with dev.to. I tried with wordpress feed url (works in dev.to but not on goglides.dev). It's something on my hosted forum. I tried enabling the debug log but got no results. Is there any log file I can check?
Hmmm 🤔What is your self-host configuration? Which process did you follow to get your Forem installed?
Have you run
sudo foremctl deployto ensure your Forem version is the latest version?
I am using Kubernetes. The version I am using is
quay.io/forem/forem@sha256:bdaae5653917441c0aad80717ca52396622dda98f1a1ac277d8adf16bd267f76, this is the latest update I upgraded yesterday (was seeing issue with previous version as well)quay.io/forem/forem@sha256:0c00c2cc12b19f689d7b7f7e0d54fbaf7298ad55373c5f5692590128c4dfb09a. My only concerns is non of the component throwing any error :). If you look at the logs, everything looks good. I think we are suppressing logs which is making it harder to debug.I wonder if it's something to do with nginx ingress controller proxy settings. In a selfhosted repo we are using nginx and
traefik.(github.com/forem/selfhost/blob/mai...). In my deployment I am only using nginx ingress controller. I wonder if its proxy settings causing problem. Ideally it shouldn't, but hard to tell.In the description above, I've included a debug log; do you think someone from the development teams could have a look at it? Any direction will be helpful.
This is a log when I press "Fetch Feed now" button.
Are you seeing an error message saying "Feed url is invalid" or any other error message?
I am not.. feed url is valid