toolmanz

Members
  • Content Count

    78
  • Joined

  • Last visited

Community Reputation

1 Neutral

About toolmanz

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Just a quick update - containers wouldn't start because I have a couple of nvidia graphics cards set up to do transcoding. Release Notes: This provided a clue ....eliminated the transcode part and containers are up....just chasing down a problem with access to the media files. More later.....
  2. I seem to remember some mention of this in the release notes.....lets go and have a look. This is done in order to run my PFSense router on my server. Possible????
  3. Last several lines of the syslog ......note the last line. 😠
  4. Folks, Is there anyone else that has run into this problem. All of the dockers work "except" the media service dockers. Start the container and I get execution error - bad parameter???? Not a lot to go on ....logs for Plex and Emby contain no clues either. Just once I'd like to have an update go smoothly. On to the Plex and Emby forums I guess .....🙄 Thanks in advance toolmanz
  5. All, Solved by installing a different version of delugevpn. Version: binhex/arch-delugevpn:2.0.4.dev38_g23a48dd01-3-01 Just paste this into the property sheet for delugevpn replacing the current repository and now docker network is running as it should. Delugevpn <edit> hit the advanced button in top right and replace the repository with the above version. <apply>. Cheers Toolmanz
  6. Figured out how to install the "binhex/arch-delugevpn:2.0.4.dev38_g23a48dd01-3-01" docker version. Go into your delugevpn property sheet <edit>, tick advanced in the upper right corner. You will see a line for repository. Replace the existing repository address with "binhex/arch-delugevpn:2.0.4.dev38_g23a48dd01-3-01" And hit apply. Worked right away...woo hoo! cheers Toolmanz
  7. Interested in how to do this.... 🤓 Never updated to another release other than what is available from normal releases. Thanks in advance Toolmanz
  8. It seems my "bridge network" has stopped functioning since my containers can no longer talk to each other. Sonarr can't speak with nzbget or any other docker. When I test the connection to download client in sonarr, nzbget, I get an error. Consequently, downloads aren't being done since they can't talk. Nothing has changed. The individual dockers have internet access on their own, I can manually add downloads and have them complete. I did however have to "power drain" my Dell R710 server in order to get my IDRAC6 card functioning again. Only th
  9. That is precisely what I did to revert to the last functioning version. I replaced the "latest" with "nextcloud-20.0.4". Worked like a charm. For those of you who are interested, this is the site for NC versions: https://download.nextcloud.com/server/releases/?C=M;O=A Cheers Toolmanz
  10. I have reverted back to 20.0.4 and all is working as normal. Will wait for a fix I guess.🙄 Cheers Toolmanz
  11. And here's the NC logs ....NC.server.error.logNC.server.access.log Should I set up a separate "new topic" for this??? Cheers Toolmanz
  12. I have uploaded the NGINX error.log and access.log. I think I have removed any identifiable info and replaced with generic labels plus some notes. It looks like this is where the problem is. nginx.server.error.lognginx.server.access.log Let me know if there is something else I need to edit out (always nervous doing this....🥺) I will visit the NC error log next but I think the above identifies the error. Cheers Toolmanz
  13. I had a look yesterday and the NC log shows all normal. I will do a deep dive into the logs as you suggest. I'll post back the results. Also, a number of other paltforms are reporting similiar problems. It has to be something common to a number of platforms. Thanks razoredge - will have a look around and see it that is the issue. More later.... Cheers Toolmanz
  14. Well a little more information on the problem ..... The docker is running and except for the webui seems to be functioning as expected. I did all of the maintenance as I would normally do with files and indices through OCC ..... not a problem. I checked the PHP version and it is up to date (Jan 7-2021) [php -v in terminal] "PHP 7.4.14 (cli) (built: Jan 7 2021 11:46:25) ( NTS ) Copyright (c) The PHP Group Zend Engine v3.4.0, Copyright (c) Zend Technologies with Zend OPcache v7.4.14, Copyright (c), by Zend Technologies" So th
  15. All, Just upgraded to the latest Nextcloud and now I can’t get into the docker. Latest ver 20. Running R710 Dell Server, 48 Gb ram, 30Tb space on Unraid. Docker container is linuxserver. See attached file. Here is the text in case you can’t see it: Internal Server Error The server was unable to complete your request. If this happens again, please send the technical details below to the server administrator. More details can be found in the server log. Technical details Remote Address: 192.168.1.29 Request ID: VuYu7IeO7IvoqC2iKHZl