asciimoo / morty

Privacy aware web content sanitizer proxy as a service
GNU Affero General Public License v3.0
485 stars 58 forks source link

URL in settings.yml and what else am I doing wrong #87

Closed gripped closed 4 years ago

gripped commented 4 years ago

At first I thought it was enough to start morty and just uncomment the following three lines in settings.yml

#result_proxy:
#    url : http://127.0.0.1:3000/
#    key : !!binary "your_morty_proxy_key"

Changing the key and also the port as invidious was already on 3000 so I started morty thus:

MORTY_ADDRESS=127.0.0.1:4000  MORTY_KEY=MYKEY /home/ubuntu/morty/bin/morty > morty.log 2>&1

And in settings.yml

result_proxy:
    url : http://127.0.0.1:4000/
    key : !!binary "MYKEY"

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

location /morty {
    proxy_pass http://127.0.0.1:4000;
}

changed the url in settings.yml to

    url : https://searx.informationhouse.co.uk/morty

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 image

Any ideas what I'm doing wrong. More options for the reverse proxy in nginx would be my guess but no clue what ?

gripped commented 4 years ago

Fixed URL needed a slash at the end. That was all :)

    url : https://searx.informationhouse.co.uk/morty/