Greygoose

unable to access the airsonic from web browser via

Hi guys, I am trying to get airsonic to work, i have copied my nextcloud config and changed what i see is required but its not working. i have added the airsonic A RECORD to my domain, also in the docker subdomain Id be most grateful if assistance. NEXTCLOUD server { listen 443 ssl; server_name nextcloud.domain.co.uk; root /config/www; index index.html index.htm index.php; ###SSL Certificates ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ###Diffie–Hellman key exchange ### ssl_dhparam /config/nginx/dhparams.pem; ###SSL Ciphers ssl_ciphers 'ECDHE-RSA-AES128-GCM-rr:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-rr-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:rr-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-rr-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHtE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-rr:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ###Extra Settings### ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; client_max_body_size 0; location / { proxy_pass https://192.168.1.200:446/; proxy_max_temp_file_size 2048m; include /config/nginx/proxy.conf; } AIRSONIC server { listen 443 ssl; server_name airsonic.domain.co.uk; root /config/www; index index.html index.htm index.php; ###SSL Certificates ssl_certificate /config/keys/letsencrypt/fullchain.pem; ssl_certificate_key /config/keys/letsencrypt/privkey.pem; ###Diffie–Hellman key exchange ### ssl_dhparam /config/nginx/dhparams.pem; ###SSL Ciphers ssl_ciphers 'ECDHE-RSA-AES128-GCM-rr:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-rr-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:rr-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-rr-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHtE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-rr:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA'; ###Extra Settings### ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; ### Add HTTP Strict Transport Security ### add_header Strict-Transport-Security "max-age=63072000; includeSubdomains"; add_header Front-End-Https on; client_max_body_size 0; location / { proxy_pass https://192.168.1.200:4040/; proxy_max_temp_file_size 2048m; include /config/nginx/proxy.conf; }

Spot on comment

hi again, I think i have narrowed down the issue. I stopped all dockers, then added back only the mainly used ones, then i went back to using only a couple and out of them i THINK it is to do with sonar and sabnzb I have added some pics of the setup of sonar

ok quick update. I deleted docker.img and restored only some dockers and the error happened over night. i managed to get a diagnostics.img mediaserver-diagnostics-20190514-0530.zip

I have attached a new Diagnostics file, this is after the reboot just now (the error happened again). I dont expect it will contain any details as the system is now running fine. until it does it again, randomly. mediaserver-diagnostics-20190512-0951.zip

This is the docker list on the system, in case you can see any errors

I have 32GB and 12GB allocated to VM's.

I looked at this file and it contains the file names but no DATA or information.

its doing it again guys, id really appreciate help

When i try to run diagnostics from GUI it doesn't allow, it says array unidentified. I run the diagnostics command from terminal and i get this... Warning: file_put_contents(): Only 0 of 838 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix/scripts/diagnostics on line 208 done. ZIP file '/boot/logs/tower-diagnostics-20190428-0938.zip' created.

haha Brilliant. A shot of grey goose it is

Dude, thanks. The price of a nice pint of UK beer is on paypal route to you.

Hi Binhex, I'm getting these errors, what do they man and how can i correct them please?

Thanks GilbN, works Thank you

Hi Guys, im really liking this I am however unable to get SabNZB to run in iframe, is that normal?

Nextcloud is superb, there is a space invader one video showing how to setup using reverse proxy with lets encypt. I highly recommend going that route.

Perfect squid, thanks so much. I have removed the docker that you mentioned (Krusader). If it doesn't happen this week after removing that docker i will add it back and change mapping.

I have attached diagnostics. mediaserver-diagnostics-20190303-0942.zip

Guys, Im not sure what is causing this, but it happens once a week or so.. I am unable to get diagnostics file as server has crashed, i can get it when i restart if needed.

solved it, or should i you guys did thank you

this the problem?

thanks for the help

Hey guys, Got an issue, my SabNZB doesn't show the size of my Cache drive, it gives another size which i'm not sure what it is referring too?