PeteAsking
-
Posts
691 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by PeteAsking
-
-
6 hours ago, Dynamiteboy said:
I don't see a settings -> admins in the legacy interface. You sure it still exists in Network 8.1.127? I am running this on a Dream-Machine that has a built-in controller as well.
Also not seeing that sso option setting in system -> advanced in the new interface.
I already tried creating a separate admin account as you can see as well. Unless my Mongo query is wrong, doesn't look like there a user there at all. I am restoring from 8.1.127 -> 8.1.127 so this is pretty much a non-starter.This is the command I was running mongo --port 27117 ace --eval "db.admin.find().forEach(printjson);"
https://community.ui.com/questions/How-to-recover-access-to-a-unifi-controller-when-the-admin-password-has-been-lost-/bea32e54-c8cd-4d08-ba98-b836acebfeb4All that outputs is like my email and name which shouldn't be the username?
This seems to be a know issue on the unifi forums. Can you try the site export and site import method?
https://help.cloudunifi.com/unifi/migrating-sites-with-site-export-wizard/
-
9 minutes ago, Dynamiteboy said:
Download from within the Unifi Network App
It seems this is a common issue with the Unifi controller. Here is an example here: https://community.ui.com/questions/Logins-not-working-after-restoring-backup-to-new-machine/023647bc-2953-421f-ac05-4a19072d702c
under legacy interface can you go to settings and then ‘admins’ and review the list of admins there and possible create a new one. Under the modern interface the sso option that links your unifi account on their website to your local deployment is under system - advanced and allows you to remote manage it at https://unifi.ui.com
you can try enabling this also and seeing what happens after a restore.
let me know after doing some troubleshooting like this.
-
29 minutes ago, Dynamiteboy said:
Where is that option? and should it be ticked or unticked? I had a local account setup under the owner account. I even created a separate "unraid" admin account for testing and neither are allowing me to login.
How did you create the backup?
-
2 hours ago, Dynamiteboy said:
When restoring from backup on unifi:8.1.127-unraid no users seem to migrate which does not allow me to login.
mongo --port 27117 ace --eval "db.admin.find().forEach(printjson);" shows no admin users. I remember my password fine for the local login, but nothing seems to work. Ideas?
Did you not have the ‘Sync Local Admins with SSO’ option ticked?
-
5 minutes ago, Heciruam said:
Hello,
sorry if I ask so boldly. I just have no idea what I am doing wrong.
So I set this up with the 11notes/unifi:8.1.127-unraid tag and everything else standard except the network type which is br0 with a defined IP adress.
When I check the log I see this
{"time":"2024-05-09T20:06:12.000Z","type":"INF","msg":"starting unifi controller"}
And when I try to access the webUI I get the following message on the page
Bad Request This combination of host and port requires TLS.
Does anybody know what I'm doing wrong?
Thank you in advance.Put https:// in front of the address
eg:
https://IPADDRESS:8443
-
1
-
-
2 hours ago, andyd said:
Yeah I’ll try that but since the issues don’t manifest till a few days later I’m thinking it makes sense to ensure setup is correct.
should I be changing the port? Network doesn’t matter?
A custom network should be fine so long as you are not running into the docker macvlan issues unraid have been trying to fix. I’m personally not affected so can’t tell you much about that.
-
7 hours ago, andyd said:
As a follow up to the memory issue I was having the other day...
I lowered the limit to 2048 and set extra parameters to 4GB
But ever since adding the container my server has been experiencing issues with Docker. Obviously it could be coincidental but hard to ignore.
1. I saw in a comment that the container should be on bridge network - I had it on a custom network ... does it need to be bridge?
2. I see port 1900 is being used by Plex again - should I remap the Unifi controller to another port like 1901?
Test by stopping all dockers except the Unifi one. If the issues go away then you have some sort of conflict. This troubleshooting step is mandatory if you want to get to the bottom of it.
-
1 hour ago, andyd said:
Globally as in the amount of RAM I have installed on the server? I have 48GB - it's never above half that. Didn't have any VMs running at the time either. I'll check though what's going on with usage.
Ok I'll see about getting the latest template
Ok let us know
-
1 hour ago, andyd said:
It's ...
11notes/unifi:8.1.113-unraid
And the values are the default ones - 2048 for startup and 4096 for limit
Are you saying that MEM_LIMIT and MEM_STARTUP should both be 2048?
And for Extra Parameters, set this to 8GB? What config type is that?
It seems like unraid is killing the docker. Check you didnt run out of ram globally. Test by stopping all VM’s and All dockers and starting only this one. If it starts then you have some issue above the container you must resolve.
-
12 minutes ago, andyd said:
Hi. The app has been working well for me but all of sudden it won't start and seeing the below in the logs. Anyone know what might be going on?
# A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x000014ca88aefdcd, pid=1, tid=12 # # JRE version: (17.0.10+7) (build ) # Java VM: OpenJDK 64-Bit Server VM (17.0.10+7-Ubuntu-120.04.1, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, parallel gc, linux-amd64) # Problematic frame: # C [libc.so.6+0x93dcd] # # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /usr/lib/unifi/hs_err_pid1.log #Strange, can you click on the docker and then click logs an post any output?
-
4 hours ago, vw-kombi said:
I jumped up to this later version also - not by accident but by design - changing tags to suit.
Is there anything specific to look out for in the release ? As to why it was not yet supported ?
All seems to be working for my limited stuff (USG, 2 x AP, 1 x 8port switch and 2 x flex).
No it was luckily a very minor update so unlikely to cause a problem. Of course it is supported now due to the error our side if you have any issues.
-
I agree what appears to have happened is an inadvertent push has incorrectly updated tag 8.1.113 to version 8.1.127. I suggest moving to tag 8.1.127-unraid at this time for consistency and I will have to immediately support this tag due to the error.
To track why or what happened you can use this link as I asked what happened on 11notes github (who runs the scripts that builds the images):
https://github.com/11notes/docker-unifi/issues/16
Kind regards
P
-
1
-
-
I will figure out what happened and come back to you.
-
7 hours ago, ultimz said:
Hi,
I have my repository/tag set to 11notes/unifi:8.1.113-unraid
Noticed this morning that the container said it had an update available. Did the update and the version (specified in the container) updated to 8.1.127 yet my repository/tagtag is still set to 11notes/unifi:8.1.113-unraid
Is this normal?
Edit: everything seems to be working fine after the update
What version are you running now? 8.1.127 is not supported at this time.
-
10 minutes ago, pmeledeo said:
I am unfamiliar with this. Didn't see anything about setting this up in the install instructions for this. I will do some research on the topic to get myself up to speed. And to answer the other reply's question, nothing changed IP-wise. I went ahead and removed this docker container from Unraid and just went back and installed the Unifi Controller on my PC. That is still working for now. I'd love to get it running on my Unraid server so I don't have to keep my PC on and awake at all times. I'll do a bit more research on all of this before attempting again.
Thank you for the replies and advice.This basically confirms that the ip changed since the docker/unraid has a different ip to the pc it was on before. You need to set the inform ip and do what bmartino said
-
1 hour ago, levnetet said:
Hi guys,
I have a trouble wit service stop at the end. The log shows the following:
(...)
:0 Permanent error code on channel bind request: 403 - Forbidden IP
:0 All TURN channel bindings failed
:0 Unable to read data from SCTP socket. Permanent error: (104) Connection reset by peer
:0 SCTP ingest failed
:0 SCTP ingest failed
:0 Unable to do SSL I/O
:0 webRtcId 1 terminated with code: (-2147090409) WebRTC connection interrupted from far side
:0 TCP candidates not supported yet
:0 TCP candidates not supported yet(...)
:0 Permanent error code on channel bind request: 403 - Forbidden IP
(...)
:0 All TURN channel bindings failed
:0 TCP candidates not supported yet
:0 Permanent error code on channel bind request: 400 - Empty port number in channel bind request
:0 All TURN channel bindings failed
:0 STUN id: 4; fd: 194 172.17.0.5:32995 -> 92.249.173.32:52282 (eth0) DTLS id: 14 (92.249.173.32:32995) (PEER) timed out
:0 webRtcId 3 terminated with code: (-2147090409) WebRTC connection interrupted from far side
:0 STUN id: 4; fd: 191 172.17.0.5:51377 -> 192.168.178.185:54448 (eth0) DTLS id: 19 (192.168.178.10:51377) (PEER) timed out
:0 webRtcId 2 terminated with code: (-2147090409) WebRTC connection interrupted from far sideCan you give me some advice?
Thanks a lot in advance
Cheers
Levente
Not sure what is wrong. Can you check no other dockers are running when you start it to rule out some sort of conflict and check you have enough disk space and so on. Also check your networking is logical. Seems like an error above the container.
-
7 hours ago, pmeledeo said:
I am actually having this same problem with 8.1.113. First time using this and everything during setup was just fine. Restored backup just fine. But my USG and my U6-Lite are stuck in an "Adopting" and "Offline" loop. Anyone else run into this with 8.1.113 or any suggestions? I've restarted the docker and power-cycled the devices. I didn't change anything during the docker setup. Followed the instructions.
Is the inform ip in the settings set correctly still? (inform host override)
-
12 minutes ago, MammothJerk said:
I'm trying to figure out why my container doesn't see the network traffic for the unraid server it is running on (192.168.1.111)
i did not change anything in the docker template, running "11notes/unifi:8.1.113-unraid"
I believe i set up the container without changing any settings other than disabling automatic updates.
Not sure but there probably isnt much I can do to fix it. The software works however unifi code with all the bugs they insert into it and its a closed box.
-
1
-
-
On 4/16/2024 at 5:11 AM, turnma said:
Hi. Minor thing, but the first post refers to the container by the name "unraid-controller-reborn" rather than "unifi-controller-reborn"!
Thanks. I have fixed this error now.
-
4 hours ago, CrippleZero said:
My apologies for necro-ing this post, but I had been following along and got it working; however, I am migrating from a backup and I am getting an error message that the backup is from a newer version that can't be used.
I guess, I'm wondering, how often is the app/docker updated? I would like to move off of my actual VM and move it to unRAID.
Are you using the latest tag? It was made available just a few days ago.
-
46 minutes ago, veeco said:
EDIT: I'll follow up on UI forums, looks like someone else spotted it as well:
Looking in the container, I found the files at:
`/usr/lib/unifi/webapps/ROOT/app-unifi/react/fonts/`
I see that js i properly loading, for example:
`https://192.168.3.152:8443/manage/react/js/5869.2f02b1d33b809f53b77e.js`
But the path to the fonts is missing the `manage/react` prefix:
`https://192.168.3.152:8443/fonts/UI_Sans_v8_Regular.eb36d6ff9c768a1639ca397b4dd84137.woff2`
It looks like a Unifi problem with the wrong paths, unless there is some configuration option. You can see the inline style loading the wrong path:
Thanks. Will just let unifi resolve it then.
-
26 minutes ago, veeco said:
Thanks for creating this image. I ported over with no problems.
One thing I noticed in the browser console is that font files are failing to load. I'm not sure if this expected:
I can check but I doubt it is important
-
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
|.|.|.|.|.|.|o|o|o|o|o|o|O|O|O|O|O|O|0|0|0|0|0|0|0|0|0|0|O|O|O|O|O|O|o|o|o|o|o|o||.|.|.|.|.|.|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
██████╗░███████╗██████╗░░█████╗░██████╗░███╗░░██╗
██╔══██╗██╔════╝██╔══██╗██╔══██╗██╔══██╗████╗░██║
██████╔╝█████╗░░██████╦╝██║░░██║██████╔╝██╔██╗██║
██╔══██╗██╔══╝░░██╔══██╗██║░░██║██╔══██╗██║╚████║
██║░░██║███████╗██████╦╝╚█████╔╝██║░░██║██║░╚███║
╚═╝░░╚═╝╚══════╝╚═════╝░░╚════╝░╚═╝░░╚═╝╚═╝░░╚══╝
░█████╗░██████╗░███████╗░██╗░░░░░░░██╗
██╔══██╗██╔══██╗██╔════╝░██║░░██╗░░██║
██║░░╚═╝██████╔╝█████╗░░░╚██╗████╗██╔╝
██║░░██╗██╔══██╗██╔══╝░░░░████╔═████║░
╚█████╔╝██║░░██║███████╗░░╚██╔╝░╚██╔╝░
░╚════╝░╚═╝░░╚═╝╚══════╝░░░╚═╝░░░╚═╝░░+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
|.|.|.|.|.|.|o|o|o|o|o|o|O|O|O|O|O|O|0|0|0|0|0|0|0|0|0|0|O|O|O|O|O|O|o|o|o|o|o|o||.|.|.|.|.|.|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
🅟🅡🅞🅤🅓🅛🅨 🅟🅡🅔🅢🅔🅝🅣🅢Docker tag: 8.1.113-unraid
NEW: Current recommended Home User tag: 11notes/unifi:8.1.113-unraid
NEW: Current Company/Corporate recommended tag: 11notes/unifi:8.1.113-unraid
Current Critical Infrastructure (no downtime) tag: 11notes/unifi:7.5.187-unraid
-
2
-
1
-
-
54 minutes ago, rorton said:
cheers, I thought I'd give it a go, its installed no problem, but got this message in the output:
WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap.
This message is normal, unraid does not support SWAP by default. It is an unraid limitation.
[Support] - Unifi-Controller: Unifi. Unraid. Reborn.
in Docker Containers
Posted
Just remove the docker and ssh into the server and under app data remove any reminants of the docker if there is anything. Then install again and it will be blank.