That's designed for running searx and morty locally I guess as I could see from the 'proxied' link in the search results that it was looking for monty on my PC. Whereas searx and monty are on a remote aws instance.
Now morty sort of works. But the proxied pages are stripped of all css it seems.
I've tested with two public instances that seem to offer morty, searx.sunless.cloud and searx.be, which look totally different viewing the proxfied version of this page https://en.wikipedia.org/wiki/Help! than the result with my morty proxy.
The two public instances have normal formatting wheras the page which has been through my proxy look like this
Any ideas what I'm doing wrong. More options for the reverse proxy in nginx would be my guess but no clue what ?
At first I thought it was enough to start morty and just uncomment the following three lines in settings.yml
Changing the key and also the port as invidious was already on 3000 so I started morty thus:
And in settings.yml
That's designed for running searx and morty locally I guess as I could see from the 'proxied' link in the search results that it was looking for monty on my PC. Whereas searx and monty are on a remote aws instance.
So I added this to the nginx conf file
changed the url in settings.yml to
Now morty sort of works. But the proxied pages are stripped of all css it seems. I've tested with two public instances that seem to offer morty, searx.sunless.cloud and searx.be, which look totally different viewing the proxfied version of this page https://en.wikipedia.org/wiki/Help! than the result with my morty proxy. The two public instances have normal formatting wheras the page which has been through my proxy look like this
Any ideas what I'm doing wrong. More options for the reverse proxy in nginx would be my guess but no clue what ?