jjthacker
-
Posts
8 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by jjthacker
-
-
19 hours ago, ati said:
I am struggling to figure out what happened to my container. Yesterday I had a momentary power loss which resulted in my internet going down, but my UPS kept my unRAID server online. I restored the internet and found my container GUI inaccessible a day or so later. I figure it was related to the internet loss and breaking the VPN connection. No biggie. I restarted the container to re-establish the connection and have no luck getting back into the GUI. Nothing has changed. No configuration change, nothing, but now it won't seem to work.
***snip***
I am having this problem as well, except no Internet outage in my case, just my container refusing to let me connect. My symptoms are otherwise identical.
-
This is the internal node. It even says so in the text I quoted. I don't map anything to it apart from what is in the docker template, and that shouldn't affect anything.
-
Love the app was very impressed with my initial testing, but I am having an issue with files not being converted/ignored. I have a simple "convert video" flow. When I add files to be converted, they appear momentarily on the dashboard and then disappear, not even appearing in the "library files" section. When I root through the log files I find this in one:
Quote==============================================================================
=== PROCESSING NODE OUTPUT START ===
==============================================================================
Base URL: http://localhost:5000
Address: INTERNAL_NODE
Making request[GET]: http://localhost:5000/api/node/by-address/INTERNAL_NODE
Waiting on node task
Completed node task
Node SignalrUrl: http://localhost:5000/flow
Making request[GET]: http://localhost:5000/api/library-file/2f233b7d-48ae-469d-8482-236b798319e2
Making request[GET]: http://localhost:5000/api/library/5ca1e8eb-96db-4b69-b56b-2298bbfde72c
Library file does not exist, deleting from library files: /media/SabNZBD/complete/Snowpiercer.S03E02.720p.HEVC.x265-MeGusta.mkv
Making request[DELETE]: http://localhost:5000/api/library-file
Exit Code: 0==============================================================================
=== PROCESSING NODE OUTPUT END ===
==============================================================================
My issues are:
a) the files definitely exist, are still in the indicated initial folder and are not deleted
b) the files never appeared in the library files section of the UI at all
This is happening with every file
Any ideas what could be causing this and how I can fix it? Thanks.
-
Has anybody figured out the SESSION ERROR problem? I am another of those affected by this.
I can log in the initial front end page, but only if I use my external domain name. It won't work if I refer to the site using the IP address. It also fails when I try to connect to the admin page, either using IP address or domain name.
I think that it is probably related to my LetsEncrypt proxy configuration, but I don't understand why it broke at the last update. It worked fine until then.
I looked at the link kindly provided by aptalca, but none of the suggested issues seem to belong to my configuration. I already had default and admin locations in my proxy configuration.
-
6 minutes ago, aptalca said:
It's been discussed to death. Harmless lua error. Unrelated.
Server ready means nginx is up and running. Check your dns settings and port forwarding
Thanks for the advice. Turns out that the port forwarding on my router was screwed up when I changed the NIC in my server. Turns out it did port forwarding by MAC address not IP address.
-
-
I am getting the same problem as Tabraxis.
[Support] uberchuckie - observium
in Docker Containers
Posted · Edited by jjthacker
My Coral dual PCIE is not being detected. I have the Coral drivers installed and their details are shown in the attached screenshot.
[QUICK NOTE]
I have just borrowed a friend's USB Coral and changed the config file to reflect this and it worked perfectly.
In the logs the following appears: