"The media could not be loaded" error.

[MaestroJAL]

Describe the bug
For a brief moment, everything was working then no media. I wonder if my instance has been blocked.

To Reproduce
Steps to reproduce the behavior:

1. I'm not sure you can reproduce it.
2. I am using docker.

Expected behavior
Media to be available - both videos and pictures are currently broken

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Ubuntu 20.04
• Browser: Chrome
• Version: 88.0.4324.150

Smartphone (please complete the following information):

• OS: iOS 14
• Browser Safari
• Version ??

Additional context
I've rebuilt the containers a few times making sure of permissions and suggestions.

[FireMasterK]

What do you see in your devtools's network tab?

[MaestroJAL]

Looks like a lot of 503 and 404 errors. Example:

502
https://***.***.***/vi/tJPIj0-pYp4/hq720.jpg?sqp=-oaymwEjCOgCEMoBSFryq4qpAxUIARUAAAAAGAElAADIQj0AgKJDeAE=&rs=AOn4CLBXrFkIGva1PD3pRJKzWRbxySBXoA&host=i.ytimg.com

404
https://***.***.***/api/manifest/dash/expire/1613606918/ei/plstYP_MIs7ayQWFnLewCw/ip/***.***.***.***/id/bc67da2a9ba9e9d2/source/youtube/requiressl/yes/playback_host/r7---sn-axq7sn76.googlevideo.com/mh/OK/mm/31%2C26/mn/sn-axq7sn76%2Csn-4g5e6nl7/ms/au%2Conr/mv/m/mvi/7/pl/20/tx/23977102/txs/23977102%2C23977103%2C23977104%2C23977105%2C23977106/hfr/all/as/fmp4_audio_clear%2Cwebm_audio_clear%2Cwebm2_audio_clear%2Cfmp4_sd_hd_clear%2Cwebm2_sd_hd_clear/initcwndbps/526250/vprv/1/mt/1613585083/fvip/5/keepalive/yes/itag/0/sparams/expire%2Cei%2Cip%2Cid%2Csource%2Crequiressl%2Ctx%2Ctxs%2Chfr%2Cas%2Cvprv%2Citag/sig/AOq0QJ8wRgIhALKbEqZh6UR1z6ZKw_lAbzMqAtdQHmVD5P3Y7NeA5TV7AiEA-3vuwkxPXcFTroXKab5kzUQ7AWUT5zC-JE1b_PLNMqs%3D/lsparams/playback_host%2Cmh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps/lsig/AG3C_xAwRgIhAORz71iA0EkJgPc0tRfc4fwm7C9OFb__M68Trx-O-WneAiEA-GyxEYAHH625xi9xUOSj9RqEl1ZWOfITOSOO73mfzAs%3D&host=manifest.googlevideo.com

[FireMasterK]

Is your video a Livestream by any chance?

For the 502, I suspect that the ytproxy isn't working, could you get logs for that?

[MaestroJAL]

The video in question is not a livestream. I've tried several searches for just random videos. The results load but with broken images. There don't seem to be any logs for the ytproxy. Could both the 404's and the 502's be proxy related?

[FireMasterK]

The 502s are because of an improperly configured reverse proxy.

The 404 is likely because something is broken in Yotter, maybe @pluja knows better as to why this happening.

It seems like a dash URL, which is really strange to me.

[MaestroJAL]

Ok. I figured it out. For some reason, even though I copied and pasted the chmod command from the installation page, the actual http-proxy.sock was not changed. I'm not sure why. The enclosing folder had the correct owner. Weird. At any rate, I fixed that and seems like everything is now working. Even the 502's are gone. Thank you for helping me out!

Update: I spoke too soon. The 502's have changed to 500's which are internal server errors, I think. Ideas on that?

[FireMasterK]

Could you paste the response of the request here? (You should click on the request, and click on the response tab)

[MaestroJAL]

This is what tries to load: https://***.***.***/ytc/AAUvwnjxERSyYfS0t6PVHYYOjYiv6AoVyBSs_8hPRFJaxQ=s48-c-k-c0xffffffff-no-rj-mo?host=yt3.ggpht.com

If I try to access it directly, I see the Yotter 500 error page. Under the 'Network' tab and under 'Request', it says: "No parameters for this request" Is this what you're looking for?

[FireMasterK]

If I try to access it directly, I see the Yotter 500 error page. Under the 'Network' tab and under 'Request', it says: "No parameters for this request"

This is really strange since the URL you send contains parameters, I will try investigating this.

I suspect you get the error 500 because of a faulty nginx configuration, could you upload your configuration here?

[MaestroJAL]

This is what I'm surrently using. Maybe it's my 301 redirect? I've been messing with restrictions but have them off for now. If I can rule out the 500 errors, Yotter would be fully functional. I should also note that Twitter calls are also receiving the 500 errors as well.

server {
    listen 80;
    server_name ***.***.***; # ChangeME
    return 301 https://$host$request_uri;
    access_log off;
}

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    include /etc/nginx/***.***.***/ssl.conf;
    # include /etc/nginx/***.***.***/security.conf;
    # large_client_header_buffers 4 16k;
    # client_max_body_size 512M;
    # index index.php index.html index.htm;
    server_name ***.***.***;
    access_log off;

    location / {
        proxy_pass http://127.0.0.1:2019; #Changed from original due to Reverse Proxy
        proxy_http_version 1.1;
        proxy_set_header Connection "";
        # auth_basic "Restricted";
        # auth_basic_user_file /var/www/***.***.***/.htpasswd;
    }

    location /static/ {
        root /docker/Yotter/app/; # Change this depending on where you clone Yotter
        sendfile on;
        aio threads=default;
    }

    location ~ (^/videoplayback$|/videoplayback/|/vi/|/a/) {
        proxy_pass http://unix:/var/run/ytproxy/http-proxy.sock;
        add_header Access-Control-Allow-Origin *;
        sendfile on;
        tcp_nopush on;
        aio_write on;
        aio threads=default;
        directio 512;
        proxy_http_version 1.1;
        proxy_set_header Connection "";
    }
}