eaglephantom
-
Posts
21 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by eaglephantom
-
-
I'm getting the same 'unable to connect' error and this is the only error I'm seeing in the log:
2023-07-15 14:19:23,285 DEBG 'watchdog-script' stderr output:
/usr/include/c++/13.1.1/bits/stl_vector.h:1125: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = std::__cxx11::basic_string<char>; _Alloc = std::allocator<std::__cxx11::basic_string<char> >; reference = std::__cxx11::basic_string<char>&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
Edit: I forgot to mention, this error is the last thing in the log and it hangs after that.-
1
-
-
2 hours ago, dawhit said:
Yes, I have the Shinobi on a VLAN. I followed @SpaceInvaderOne setup. I also have pfsense setup in VM that the VLAN is configured on.
Odd, I'm using a similar setup except OPNsense and it's not a VM it's on a physical router. I have the VLAN properly set up on my router and switch. It was previously working for me and suddenly stopped after one of the updates. I'm on 6.11.5 as well.
-
On 12/1/2022 at 10:24 PM, dawhit said:
Please check your shinobi.subdomain.conf in your proxy-conf folder. find "set $upstream_app shinobi;" I changed this to "set $upstream_app myipaddress;" that is the address of my shinobi container. When I changed this, my swag reverse proxy started working correctly.
Hope this helps.
I've tried that in the past and it didn't work. I just tried again and it's the same result. I think it's an issue with newer versions of Unraid having a bug that won't allow SWAG to work with containers that are on custom networks aka VLANs. Is your shinobi container assigned to a VLAN? User @ax77 above is having the same problem I'm having.
-
On 11/22/2022 at 4:07 AM, pkoasne said:
I had to add write permissions to the /appdata/matrix folder to get it to write the config files.
That helped, now the files are in the folder, and I edited the config yaml, but now I'm getting "unsupported database type" when I try to run the container. I have the db up and running in a postgresql14 container and I pointed the yaml file to the correct place. Odd.
-
I'm getting an "unsupported database type" error after editing the yaml file and restarting the matrix container... Anyone else get that at first?
-
Hello-
I'm attempting to install Matrix using this guide:
https://forums.unraid.net/topic/127917-guide-matrix-synapse-w-postgres-db-chat-server-element-web-client-coturn-voice/I've followed all the steps appropriately leading up to the part where I install Matrix from Community Apps, and so far everything is done correctly (I think). When I attempt to install Matrix, there seems to be a permission error prevalent in the container log. Here's what shows up:
/start.sh: line 14: /data/turnserver.conf: Permission denied /start.sh: line 15: /data/turnserver.conf: Permission denied /start.sh: line 16: /data/turnserver.conf: Permission denied /start.sh: line 17: /data/turnserver.conf: Permission denied /start.sh: line 18: /data/turnserver.conf: Permission denied /start.sh: line 19: /data/turnserver.conf: Permission denied /start.sh: line 20: /data/turnserver.conf: Permission denied /start.sh: line 21: /data/turnserver.conf: Permission denied Traceback (most recent call last): File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main return _run_code(code, main_globals, None, File "/usr/lib/python3.10/runpy.py", line 86, in _run_code exec(code, run_globals) File "/usr/local/lib/python3.10/dist-packages/synapse/app/homeserver.py", line 413, in <module> main() File "/usr/local/lib/python3.10/dist-packages/synapse/app/homeserver.py", line 403, in main hs = setup(sys.argv[1:]) File "/usr/local/lib/python3.10/dist-packages/synapse/app/homeserver.py", line 311, in setup config = HomeServerConfig.load_or_generate_config( File "/usr/local/lib/python3.10/dist-packages/synapse/config/_base.py", line 739, in load_or_generate_config with open(config_path, "w") as config_file: PermissionError: [Errno 13] Permission denied: '/data/homeserver.tmp' awk: cannot open /data/homeserver.tmp (No such file or directory) mv: cannot create regular file '/data/homeserver.tmp': Permission denied mv: cannot stat '/data/homeserver.tmp': No such file or directory sed: can't read /data/[my chat.domain here].log.config: No such file or directory -=> generate turn config -=> generate synapse config Generating config file /data/homeserver.tmp -=> configure some settings in homeserver.yaml -=> configure some settings in [my chat.domain here].log.config -=> you have to review the generated configuration file homeserver.yaml ** Press ANY KEY to close this window **
When I use the terminal to view /mnt/user/appdata/matrix, there's nothing in the folder. Before attempting to install the Matrix container I did what the above guide said (set my network type to my proxynet, which works with other reverse-proxied containers of mine, and set my server name to my chat domain). I also double-checked my SWAG conf file for Matrix and everything looks correct. My CNAME is added in Cloudflare and points to my DuckDNS domain for my home network, and proxy is not enabled, just "DNS only".
Any ideas on why this permission error is happening?
Unraid with Matrix install: version 6.10.3
2nd Unraid with SWAG install: version 6.11.4
-
1
-
-
On 9/26/2022 at 12:09 PM, ax77 said:
6.11.0 has been released. Won't have time to test it for a couple of days
I upgraded to 6.11.0 and the issue is still there. Also one of my drives failed shortly after upgrading but I'm sure that's unrelated. Hopefully that's just a bad SATA cable.
-
5 hours ago, ax77 said:
do you remember if it stopped working around the time you upgraded?
I'm not sure. I can only revert back to 6.10.2, but I want to say the problem happened either with that upgrade or prior. I can try reverting to 6.10.2 and see if it works.
-
1 hour ago, ax77 said:
yeah there's a restore option in Update OS. What version are you on? I haven't been able to find anyone reporting this issue
I'm on 6.10.3
-
On 9/18/2022 at 10:59 AM, ax77 said:
@eaglephantom What unraid version are you running?
I just upgraded from 6.9.2 to 6.10.3 and now my shinobi reverse proxy doesn't work. All other reverse proxies work. I restored version 6.9.2 and the shinobi reverse proxy works again. Try restoring your previous OS. I'm not sure what about the new version is causing this but at least we're getting somewhere. Let me know.
Ah dang... I really don't want to have to revert back to 6.9.2 (is that even easy to do?)
I wonder if Ed has already identified the issue. -
19 hours ago, ax77 said:
did you check your proxy conf?
Sorry but, check for what?
-
11 hours ago, ax77 said:
did your IP address change? do you have swag pointed to a dynamic dns provider for shinobi? 502 bad gateway means theres no connection made.
It didn't change, but I have the cname setup in cloudflare to point to my duckdns domain. I went and checked just now and duckdns has my current address.
-
On 8/28/2022 at 7:32 PM, kulezero said:
I am having the exact same problem with my shinobi install. Everything is working perfect except for the reverse proxy part. I checked the error log in nginx and its the same error you are getting. Hopefully someone with some knowledge on this will see it.
And I'm assuming you tried ax77's solution and it didn't work? I had a glimmer of hope when I saw his post
-
On 8/23/2022 at 12:25 PM, ax77 said:
I've had that problem before. Go into Docker settings and disable "custom networks" restart docker then shut it down and re-enable custom networks. That brings it back for me every time. Not sure why it happens but seems to happen sometimes after a server reboot.
On another note I'm still dealing with shinobi not purging old recordings and filling up my drive. I'm getting tired of manually deleting them. No one else seeing this?
Thanks for your response. I tried that out and it didn't work, unfortunately. After doing what you said I also restarted both swag and shinobipro and it's still not working. I'm getting a bunch of this in the error.log within /mnt/user/appdata/swag/log/nginx:
2022/08/27 18:37:15 [error] 305#305: *183 connect() failed (110: Operation timed out) while connecting to upstream, client: 192.168.1.1,
I cut off the rest but that 192.168.1.1 is my router, so I'm wondering if the issue is there but I have the vlan set up properly... I'm not sure what would've changed. I looked in syslog for my router and didn't see anything that stands out.
-
I was previously able to access my ShinobiPro instance via swag but now I'm getting 502 bad gateway errors. I'm still able to access other containers (such as Nextcloud) via swag. I didn't make any changes other than reinstalling Shinobi with the same settings as before, same VLAN and all of that. I also have the "custom networks" setting turned on in the Docker settings. I looked over the config for it in swag and everything looks good. Is anyone else having this issue recently?
-
Hi Everyone,
I'm hoping someone here can help me figure this out. I hadn't logged into the Shinobi web ui in a while and then I tried recently without success. My shinobipro docker log is saying that various tables do not exist, such as shinobi.Schedules, shinobi.logs, etc. (attached a section of the log), and when I went into the mariadb logs via terminal I found a lot of "error 81" messages saying that Shinobi doesn't have permission to access the db. (attached a section of that log as well).
It was all working fine before, I never changed anything, and I'm not sure when this issue started. Currently on Unraid 6.10.1 (not sure if the issue started after the Unraid OS update).
[Support] binhex - DelugeVPN
in Docker Containers
Posted
Before my issue above I had updated to 6.12.2 and it broke a few other things, so I reverted back to 6.11.5. I'm not sure if that's what caused the error, but I did have to force update all of my containers to get them to start up without "execution error". Did anyone else experiencing problems update Unraid and then revert back like I did?