-
Notifications
You must be signed in to change notification settings - Fork 67
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
upgrading searx-docker broke it #58
Comments
If I'm not mistaken it's the |
Can you check if there are errors in Firefox Development tool:
Also can you check your uwsgi.ini ? |
In this whole process I noticed that the problem does not exist if I use the unmodified Caddyfile. Once I change the http and https port settings there, I can reproduce the problem reliably. |
First: I see example.com everywhere, I guess you have redacted your hostname ? The CSP headers block the loading ( I guess if you comment out this block Lines 77 to 84 in 7ad4d49
it will work, but this is not the solution.
How do you specify the HTTPS / HTTP ports ? According to https://caddyserver.com/docs/caddyfile/options you can replace Lines 1 to 3 in 7ad4d49
by
|
Thank you for your guidance.
I am sorry, I should have specified it. Yes, I redacted my hostname, its IP number and the port.
I agree, it was working before the update with this block not commented out.
I essentially have the same syntax with port numbers in 20000s, which again used to work without problem before the update... Another thing I failed to mention is there is another docker container on this host that serves an nginx instance at port 80, and that is the reason why I changed the port settings for searx. I don't think this would be the deal breaker either, since both containers were fully functional before the update. Nginx container is still functional at this time. |
Is there no suggestion about how to fix this? I tried rebuilding the container from scratch but the service did not start when Caddyfile was modified to include the following lines:
Is there a way to publish the container ports to the host other than 80 and 443? Modifying the Caddyfile does not seem to work anymore. |
Hi,
This is what I did:
sudo systemctl stop searx-docker.service
docker-compose pull
sudo systemctl start searx-docker.service
This is now what I have:
As you can see the web page does not render correctly and the 'Start search' button does not work.
I did not change anything else other than what was mentioned above. Your guidance will be greatly appreciated.
Additionally, after posting this message, I recloned this git repository, modified the files .env and Caddyfile to my settings and retried with the same outcome. I tried accessing the site both with Firefox and Chromium with the same results.
The text was updated successfully, but these errors were encountered: