skyline7349

Would be cool to have a Favorites section on the dashboard page.

you were right, i rebooted and the password was reset, So i did passwd to get into UI again and updated the password in the users tab, works fine now. Thank you

Thank you both, i ended up doing a passwd and creating a password that way, worked fine after that.

Yes its requiring i put text in the password box

I upgraded from 6.9 to 6.10 and now im presented with a login script. My root user doesnt have a password so im not sure how to login to my dashboard now. I can access the server via ssh

No i meant the actual docker service not a docker container

How would i restart docker service via script? Sometimes when i do a force shutdown and power back on. Dockers wont start and say no container. So if I go to settings and disable docker and reenable everything is fine. Is there a way to do this via script?

Anyone have the issue when restarting sometimes you have to reclaim the server? Happens to me around once a week.

I it just me or is it annoying that the Username and password fields are on different pages and the focus isnt on the boxes. I have to click username box input username then go to next page and click the password box then put password again. Is there a way to change this?

How do i route all data through the VPN? When i connect to VPN and check IP its same as when not connected. **EDIT** So i see theres a redirect-gateway. I enabled this and i can still access local websites but i cant access any other website.So then i changed the DHCP server to google and now im showing the VPN IP. Just put this here incase someone else is in need.

Is it just me or does the container not work? Im getting this in log. 2017-06-05 11:41:17,644 DEBG 'flexget-script' stdout output: 05.06.2017 11:41:17 : Starting DAEMON 2017-06-05 11:41:17,645 INFO success: flexget-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-06-05 11:41:19,901 DEBG 'flexget-script' stdout output: 2017-06-05 11:41 CRITICAL manager [/] The keys `api`, `webui` are not valid here. 2017-06-05 11:41:19,901 DEBG 'flexget-script' stdout output: 2017-06-05 11:41 CRITICAL manager Failed to load config file: Did not pass schema validation. 2017-06-05 11:41:19,901 DEBG 'flexget-script' stderr output: Could not start manager: Did not pass schema validation. 2017-06-05 11:41:21,795 DEBG 'flexget-script' stdout output: 2017-06-05 11:41 CRITICAL manager [/] The keys `api`, `webui` are not valid here. 2017-06-05 11:41:21,796 DEBG 'flexget-script' stdout output: 2017-06-05 11:41 CRITICAL manager Failed to load config file: Did not pass schema validation. 2017-06-05 11:41:21,796 DEBG 'flexget-script' stderr output: Could not start manager: Did not pass schema validation. 2017-06-05 11:41:21,901 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47863564692728 for <Subprocess at 47863564692368 with name flexget-script in state RUNNING> (stderr)> 2017-06-05 11:41:21,901 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47863564692440 for <Subprocess at 47863564692368 with name flexget-script in state RUNNING> (stdout)> 2017-06-05 11:41:21,902 INFO exited: flexget-script (exit status 1; not expected) 2017-06-05 11:41:21,902 DEBG received SIGCLD indicating a child quit

Is it possible to setup this docker to use a socks5 proxy?

Is anyone having issues with CPU? Mines using 96% of a core.

So im trying to configure proxy pass for this docker to point example.com/request to my plex request docker. Ive been looking on this forum and internet and no solutions seem to work. I made my server config very simple server { listen 80 default_server; server_name _; location / { #include /config/nginx/proxy.conf; proxy_pass http://192.168.1.90:3000; } #return 301 https://$host$request_uri; } This works and shows my the plex request page. When i make it this. server { listen 80 default_server; server_name _; location /request { #include /config/nginx/proxy.conf; proxy_pass http://192.168.1.90:3000; } #return 301 https://$host$request_uri; } it doesnt work. Ive also tried with location as /request/ That didnt work either. So my letsencrypt docker is setup to have external port of 83. When i go to http://192.168.1.90:83/request/ for some reason it redirects the url to http://192.168.1.90/request/ which isnt correct. Does this have something to do with setting up other proxy headers?

Hey, I dont quite understand this. I have letsencrypt running on 80 and 443. Then i have nextcloud running on 444 like you said. Im trying to do it like server.com/nextcloud not nextcloud.server.com is this an issue? The config you provided is that for the letsencrypt server?