Everything seems to be working a ok, sidekiq is, no obvious errors nor warnings.
Some other bits - e.g category banners - installed via popular okey.
ver. 3.0.5 / 461966e028
I’ll try zip
Not sure if that did it - perhaps destruction & creation of the container did - but now with updated to 3.0.6 version, Discourse can install CHL via popular.
I keep getting that error for all/any theme &| component now.
Do these work - I’m asking for when I go to “Preview” I get redirected to: Theme Creator with a pup-up and a button “View Theme” which if I go for I end up at ‘discourse - Theme Creator’
Yes. btw - should “standard” install end up having dev release (mine shows 3.2.0.beta1-dev) ?
In some logs I see:
…
Processing by Admin::ThemesController#import as */*
Parameters: {"remote"=>"https://github.com/discourse/discourse-category-banners"}
Rendered text template (Duration: 0.0ms | Allocations: 1)
Completed 418 in 2ms (Views: 0.4ms | ActiveRecord: 0.0ms | Allocations: 1273)
Failed to process hijacked response correctly : Timeout::Error : Timeout::Error
Would the fact that I have Nginx proxy external to the host/node play a role in it? (everything seems to work normal)
From within container I can curl those URIs — of view of some component which fail with 500 — just a ok.
Is there a way to get more verbose debug for those bits?
Components installed via zip seem to work okey.
I’d not think so, 4 core 8GB of RAM and it’s only freshly installed lab - the very moment Discourse fails that way I can curl, within the container, that same URI just fine.
What I think would be helpful here is if I knew how to get/make logs more verbose/debugged - if devel reads here perhaps can advice on that.
Looking back over this, my guess is that you have a docker config problem and it cannot access github. But I’m not sure how that could be true if you did a standard install, as it would have cloned plugins from inside the container.
These are the logs I pasted already, earlier - I still hope those could be made more verbose & telling.
I also said, in my last comment, that I can curl those very URI of the component which is Github URI, just fine, within the container - you think what you said, docker config, might be the issue really?