Iceman1199

Members
  • Posts

    26
  • Joined

  • Last visited

Posts posted by Iceman1199

  1. 8 hours ago, cat2devnull said:

     

    So you have to get NextCloud to rescan the existing data folder and add all the files to the database.

    php occ files:scan --all

    Yup, I found a command similar last night and everything was added back. Was even able to add back my users with their data. 

  2. 3 hours ago, johnwhicker said:

    yes everything

    How did you remap your existing data to your new nextcloud setup?  My data exist on my array, but I guess when I setup nextcloud, it created a new database in my nextcloud share, and now Nextcloud is only looking at that database for files. 

  3. I get something similar to @johnwhicker, except mine is telling me the next update is Nextcloud 17.0.10, and my channel is beta. IT says my current version is 26.0.2, but even in the GUI its asking me to update, which fails giving the same error about updates/downgrades between major versions not supported. Not sure what went wrong and I've been at it for almost two days.  Any help would be greatly appreciated. 

     

     

    6-2-2023 12-58-13 PM.png

    6-2-2023 1-01-51 PM.png

    6-2-2023 1-02-30 PM.png

  4. 1 hour ago, johnwhicker said:

    None of the steps here work for me and I think my NextCloud is even more screwed up than before I started. 

     

    Can I just delete NextCloud and re-install it?  Would I lose the settings and content?
     

    So frustrating and annoying :( 

    I'm in the same boat.  I tried @Danuel @allinvain and @dodgypast steps.  I even get the error about permissions being needed, but they are correct from what I can tell. 

     

    And when I try to run the docker exec -it nextcloud updater.phar command, I get this mess:

     

    Nextcloud Updater - version: v26.0.0beta2-9-g64e2e4c dirty

    Current version is 26.0.2.

    Update to Nextcloud 17.0.10 available. (channel: "beta")
    Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-17.0.10.zip
    Open changelog ↗

     

    Why is it looking for 17.0.10 and even beta now? Really just thinking about blowing it all away and restarting lol. 

     

    Thoughts?

  5. 7 minutes ago, Qzack7 said:

    Hi Everyone, I encountered a strange bug when running a docker update today.

     

    The update caused the Server and Node to remove itself from 2 different servers. It seems like the 'Node Port:' variable got duplicated causing failures.

     

    Removing the extra/duplicate 'Node Port:' line on the update container screen fixed everything.

     

    I was able to remove the extra "Node Port" on the tdarr docker template, but I still get an install failure for the tdarr node.  Any suggestions?

  6. 1 hour ago, theshabobo said:

    I am having the exact same issue. @binhex can you please update the container to the newest version so all of us having issues can get it resolved. Thank you! :)

     

    EDIT: Update ran. to version .1999 This fixes the issue. 

    NOTE: you may have to remove and re-add the IPT entry in Jackett

     

    Yup...just did a force update and configured IPT with cookies and had no issues.  

  7. 57 minutes ago, Byrd said:

    If anyone is having issues with IPT, the website layout was updated and cookies are broken. The official Jackett container has fixed this in the newest version.

    I'm having this issue due the IPT's update.  I see where you can manually add the cookies with the supplied directions, but I'm still getting an error about 

    " An error occurred while updating this indexer
    Your cookie did not work: Found 0 results in the tracker"

     

    Has anyone been able to get passed this part?

  8. 5 minutes ago, Iceman1199 said:

    Wow!!! I feel like an idiot.  That is exactly the reason why.  Any thoughts on how to get around that?  Grafana is using port 3000.  I worry just changing the port on the Rocketchat docker won't work.  

    Scratch that last thought.  I just changed the port on Grafana instead and I got RocketChat up.  Thanks for the fix bro!!!!

  9. 5 minutes ago, SpaceInvaderOne said:

    So you get an error like this when you click on start for the container?

    1419237096_ScreenShot2020-06-13at17_43_12.png.5ae1c17edd80190a8afa05ca7fe3387b.png

     

    Most likely you have another container running with the same port in use. Is anything else using port 3000?

    Grafana also uses port 3000 by default.

    Wow!!! I feel like an idiot.  That is exactly the reason why.  Any thoughts on how to get around that?  Grafana is using port 3000.  I worry just changing the port on the Rocketchat docker won't work.  

  10. 6 hours ago, SpaceInvaderOne said:

     

     

     

     

    Here is a guide showing how to setup Rocket chat running through a reverse proxy.

    Also you can update the container but when you setup the mongoDB you must specify the hostname in the container when you create it.

    That way when the container is ever recreated it keeps the same name and so doesnt cause the database to break.

     

    If you already have rocket chat installed and  have disabled updates then see a fix that will allow you to update  as normal at the end of my video.

     

     

    Thanks SpaceInvader One.  I'm following your guide, but when I try to start up RocketChat docker I get a "Execution Error:Server Error".  Any ideas on what might be causing this?

  11. On 5/18/2020 at 12:14 PM, Maelstromeous said:

    Hello,

     

    I've been attempting to fix this issue but it's causing me significant pain. It appears that NZBGeek (who use Cloudflare) has (rightfully) increased their TLS version to 1.2, and it appears the docker image has an older version of Mono which makes it incompatible. I'm using binhex-delugeVPN and using PIA as the VPN source.

     

    I'm getting this error when attempting to use the indexer, and/or when I perform a test, been getting this since error:

    
    System.Net.WebException: Error: ServerProtocolViolation: 'https://api.nzbgeek.info/api?t=caps&apikey=FOO' ---> System.Net.WebException: Error: ServerProtocolViolation
      at System.Net.WebConnectionTunnel.ReadHeaders (System.IO.Stream stream, System.Threading.CancellationToken cancellationToken) [0x000cf] in /build/mono/src/mono/mcs/class/System/System.Net/WebConnectionTunnel.cs:206 
      at System.Net.WebConnectionTunnel.Initialize (System.IO.Stream stream, System.Threading.CancellationToken cancellationToken) [0x00325] in /build/mono/src/mono/mcs/class/System/System.Net/WebConnectionTunnel.cs:171 
      at System.Net.WebConnection.CreateStream (System.Net.WebOperation operation, System.Boolean reused, System.Threading.CancellationToken cancellationToken) [0x001ff] in /build/mono/src/mono/mcs/class/System/System.Net/WebConnection.cs:233 
      at System.Net.WebConnection.InitConnection (System.Net.WebOperation operation, System.Threading.CancellationToken cancellationToken) [0x000f7] in /build/mono/src/mono/mcs/class/System/System.Net/WebConnection.cs:263 
      at System.Net.WebOperation.Run () [0x00052] in /build/mono/src/mono/mcs/class/System/System.Net/WebOperation.cs:268 
      at System.Net.WebCompletionSource`1[T].WaitForCompletion () [0x0008e] in /build/mono/src/mono/mcs/class/System/System.Net/WebCompletionSource.cs:111 
      at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task`1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func`1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000e8] in /build/mono/src/mono/mcs/class/System/System.Net/HttpWebRequest.cs:956 
      at System.Net.HttpWebRequest.GetResponse () [0x0000f] in /build/mono/src/mono/mcs/class/System/System.Net/HttpWebRequest.cs:1218 
      at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0011b] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:82 
       --- End of inner exception stack trace ---
      at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x001ca] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:113 
      at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0003c] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\FallbackHttpDispatcher.cs:35 
      at NzbDrone.Common.Http.HttpClient.ExecuteRequest (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookieContainer) [0x0007e] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:121 
      at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00008] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:57 
      at NzbDrone.Common.Http.HttpClient.Get (NzbDrone.Common.Http.HttpRequest request) [0x00007] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:264 
      at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.FetchCapabilities (NzbDrone.Core.Indexers.Newznab.NewznabSettings indexerSettings) [0x0009a] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:62 
      at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider+<>c__DisplayClass4_0.<GetCapabilities>b__0 () [0x00000] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:35 
      at NzbDrone.Common.Cache.Cached`1[T].Get (System.String key, System.Func`1[TResult] function, System.Nullable`1[T] lifeTime) [0x0006a] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Cache\Cached.cs:81 
      at NzbDrone.Core.Indexers.Newznab.NewznabCapabilitiesProvider.GetCapabilities (NzbDrone.Core.Indexers.Newznab.NewznabSettings indexerSettings) [0x00020] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Indexers\Newznab\NewznabCapabilitiesProvider.cs:35 
      at NzbDrone.Core.Indexers.Newznab.Newznab.get_PageSize () [0x00000] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Indexers\Newznab\Newznab.cs:23 
      at NzbDrone.Core.Indexers.Newznab.Newznab.GetRequestGenerator () [0x00000] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Indexers\Newznab\Newznab.cs:27 
      at NzbDrone.Core.Indexers.HttpIndexerBase`1[TSettings].TestConnection () [0x00007] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:334 

    Steps taken:

    1. Attempt to use http instead of https (would have been horrible if I had to use that)
    2. Changed STRICT_PORT_FORWARDING in binhex-delugevpn container to "no" and restarted the Sonarr / Radarr containers and binhex, didn't work
    3. Double checked (within the container itself) what the VPN region is, which is France, which appears to support strict port forwarding.

     

    Versions:

     

    Version

    2.0.0.5344

    Mono Version

    6.4.0

     

    Would anyone be able to advise what to do next?

     

    Thanks in advance!

    I am also having this same issue.  In addition, early this morning my logs notate that all my indexers aren't able to connect.  Jackett says there are no issues on its side.  i just checked Radarr and the same now.  Also noticed I cannot add any new shows/movies as it comes back with an error.  

  12. 59 minutes ago, NLDer said:

    Are you stopping the docker before moving the file in? It can't be running while you do that 

    Yes, I am stopping the docker before moving the .conf file

  13. Was checking to see if anyone could provide any insight for me.  I have followed SpaceInvaders One's newest video setup (I previously used his for letsencrypt and such so that part was done already).  Once I load the jitsi .conf file into the letsencrypt proxy-conf folder and restart the letsencrypt docker, it start throwing errors, yet letsencrypt still works for other applications. The errors state:

     

    nginx: [warn] could not build optimal variables_hash, you should increase either variables_hash_max_size: 1024 or variables_hash_bucket_size: 64; ignoring variables_hash_bucket_size

     

    Any thoughts on how to adjust the .conf file in order to remove this warning?

     

    Also noticed that I can hit jitsi from my internal network, but when trying to hit it through the reverse proxy I get the "Welcome to our Server: The website is currently being setup under this address."

     

    Thanks in advance.  

  14. 8 minutes ago, Kewjoe said:

    Not bothersome. What version are you on? and what are you trying to upgrade to? Can you paste your config.php (remove the sensitive bits)

    Per the config.php file I'm on 16.0.8.1.  I was trying to go to the next available, which was 17-something.  Can't see now as I cannot open the web gui to see.  My end goal is to update to newest stable release.  Thanks again for you help.  

     

    image.png.b350ec3df92784037da2918a0e939281.png

  15. On 3/14/2020 at 8:22 AM, Kewjoe said:

    Try this link: https://help.nextcloud.com/t/updates-between-multiple-major-versions-are-unsupported/7094/13

     

    specifically the comment by nickvergessen

     

    Talks about how the config file might have the wrong version causing the upgrade to fail.

    Thanks Kewjoe,

     

    Having difficulties understanding this comment by Nick:

     

    So what you could do is:

    Remove the version from the config.php you copy all the time

    Copy the config.php to others.config.php instead of config.php

     

    Do I remove the entire version line, or just remove the version value in place?  Also, I don't have an others.config.php file that I can locate.  Are these steps or different options as well.  I did respond to Nick as well on the Nextcloud forum for clarification. 

     

    To add now, when trying to launch the NextCloud docker I get an Internal Server Error and cannot access the web gui at all.  

     

    Sorry to sound bothersome.  

  16. 2 hours ago, Kewjoe said:

    Upgrade via command line:

     

    Thank you Kewjoe.  

     

    I followed the step, but when getting to the "Perform the Upgrade" step, I got the following error:

     

    Set log level to debug
    Exception: Updates between multiple major versions and downgrades are unsupported.
    Update failed

    Maintenance mode is kept active
    Reset log level

     

    Any thoughts?  I appreciate all the help. 

     

     

  17. Hey fam,

     

    I've been looking all over the internet for a bit for this answer and have not been able to find anything that pertains to my situation.  I'm currently on 16.0.8 trying to update to 17.0.4. Once I select the "Open updater" option I get a white page with the writing "Step 3 is currently in process.  Please reload this page later."  It was been stuck like that for almost a month now.  I can provide logs and such if needed, just need to know which ones are required before I start posting a bunch of non-needed logs.  Is anyone able to help me out here?  

     

    Thanks in advance.  

  18. Good evening,

    Tried checking the net for this, but was unable to locate an answer.  I'm following SpaceInvader Once's guide for this set up.  After I install OpenVPN AS and launch the admin web gui, the default login/password of admin/password is not working for me.  It says the password is invalid.  Its my first time trying to set it up.  Also noticed that port 1194 won't open up as well even though I have it set in my USG with it pointed to my server IP's address.  Any assistance is greatly appreciated.