spyd4r

Is anyone able to get a VM running on unraid able to talk to netboot.xyz? I have it all setup as documented in my Unifi configuration, I just get no pxe boot from a VM. edit: pxe boot happened once, and it's gone again.. it's like I am not getting the DHCP request. edit 2: I figured it out, with Unifi USG, I had to add the following dhcp options NAME: code_93 CODE: 93 TYPE: Unsigned integer 16

I'll show you my matrix.subdomain.conf file server { listen 443 ssl; listen 8448 ssl; server_name bridge.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app 10.10.4.234; set $upstream_port 8008; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header X-Forwarded-For $remote_addr; } location ^~ /_matrix { proxy_pass http://10.10.4.234:8008/_matrix; } location ^~ /_matrix/identity { proxy_pass http://10.10.4.234:8008/_matrix/identity; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } } While we're at it, in regards to your port forwards on your router, how do you have it configured? Are you using cloudflare also? I noticed a few things needed in regards to configuring DNS at cloudflare for federation to work properly. also, in regards to turnserver.conf. I think you added pidfile=/data/turnserver.pid userdb=/data/turnserver.db did you also add the no-cli?

1 thing i see right off the bat.. database: name: sqlite3 args: database: /homeserver.db should be database: name: sqlite3 args: database: /data/homeserver.db other then that the only differences between yours and mine is the listeners, I have mine setup a bit diferently. listeners: # TLS-enabled listener: for when matrix traffic is sent directly to synapse. # # Disabled by default. To enable it, uncomment the following. (Note that you # will also need to give Synapse a TLS key and certificate: see the TLS section # below.) # - port: 8448 tls: false type: http x_forwarded: false bind_addresses: ['0.0.0.0'] resources: - names: [federation] compress: false # Unsecure HTTP listener: for when matrix traffic passes through a reverse proxy # that unwraps TLS. # # If you plan to use a reverse proxy, please see # https://github.com/matrix-org/synapse/blob/master/docs/reverse_proxy.md. # - port: 8008 tls: false type: http x_forwarded: true bind_addresses: ['0.0.0.0'] resources: - names: [client] compress: true - names: [federation] compress: false Can you paste your turnserver.conf? (remove the secret)

if you want to send your conf file for matrix privately to me or paste here and make sure you remove anything sensitive. perhaps we can give you a hand.

I got a locally run dimension server up and running, noticed that was still in your todo. Let me know if you need assitance putting that together.

in regards to the pid file edit /data/turnserver.conf, add the following and restart pidfile=/data/turnserver.pid userdb=/data/turnserver.db perhaps, @yinzer should add this to the original post. I believe you can set "no-cli" in turnserver.conf as well to remove the other message. reference: https://github.com/instrumentisto/coturn-docker-image/issues/13

if you don't have ipv6 make sure you don't have it listed ['::1', '0.0.0.0'] or whatever it looked like, make sure you set it as TeddyTux mentioned above... Took me a couple minutes to notice this.

+1 would also like the ability to have it configured easily for authentication on rooms.

In the glances container, how can I make it so it can save the glances.conf to appdata so I can make some custom edits?

i was able to get a beta tag operational by editing /usr/lib/unifi-video/conf/mongodv3.6+.conf and changing it to engine: wiredTiger. i did this during a fresh install and then restored a backup.. it seems to have worked.. although in settings it still thinks its a 3.9.12 controller.

i've tried a clean install after ditching my appdata on beta, testing and latest branches.. and none will start up from scratch on a fresh install.

that didn't work for me, i just ended up rolling back to 3.9.12

I used :beta on a fresh container initialization and it still didn't work correctly.. so i'm not sure. I'm don't think it needs 4.0 as I believe Unifi is still pushing 3.4 on the cloudkeys if i am not mistaken.

This broke my install because of the wiredTiger changes, which i understand.. but I can't even get this to start on a fresh install with 3.10.1... I deleted all my existing folders in relation to the container.. Still no go, trying to gather logs. it appears it's using an older mongo conf file which uses mmap_v1? and the mongo install is still 3.4 but unifi is 3.10.1 root@e50858fa7931:/var/log/unifi-video# dpkg --list | grep -i mongo ii mongodb-org-server 3.4.19 amd64 MongoDB database server ii mongodb-org-shell 3.4.19 amd64 MongoDB shell client root@e50858fa7931:/var/log/unifi-video# dpkg --list | grep -i unifi ii unifi-video 3.10.1 amd64 Ubiquiti Networks UniFi Video controller ----- END BACKTRACE ----- 2019-02-15T14:56:11.834-0500 I CONTROL [main] ***** SERVER RESTARTED ***** 2019-02-15T14:56:11.837-0500 I CONTROL [initandlisten] MongoDB starting : pid=4189 port=7441 dbpath=/usr/lib/unifi-video/data/db 64-bit host=e50858fa7931 2019-02-15T14:56:11.837-0500 I CONTROL [initandlisten] db version v3.4.19 2019-02-15T14:56:11.837-0500 I CONTROL [initandlisten] git version: a2d97db8fe449d15eb8e275bbf318491781472bf 2019-02-15T14:56:11.837-0500 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2n 7 Dec 2017 2019-02-15T14:56:11.838-0500 I CONTROL [initandlisten] allocator: tcmalloc 2019-02-15T14:56:11.838-0500 I CONTROL [initandlisten] modules: none 2019-02-15T14:56:11.838-0500 I CONTROL [initandlisten] build environment: 2019-02-15T14:56:11.838-0500 I CONTROL [initandlisten] distmod: ubuntu1604 2019-02-15T14:56:11.838-0500 I CONTROL [initandlisten] distarch: x86_64 2019-02-15T14:56:11.838-0500 I CONTROL [initandlisten] target_arch: x86_64 2019-02-15T14:56:11.838-0500 I CONTROL [initandlisten] options: { config: "/usr/lib/unifi-video/conf/mongodv3.0+.conf", net: { bindIp: "127.0.0.1", http: { enabled: false }, port: 7441 }, operationProfiling: { mode: "off", slowOpThresholdMs: 500 }, storage: { dbPath: "/usr/lib/unifi-video/data/db", engine: "mmapv1", journal: { enabled: true }, mmapv1: { preallocDataFiles: true, smallFiles: true }, syncPeriodSecs: 60.0 }, systemLog: { destination: "file", logAppend: true, path: "logs/mongod.log" } } 2019-02-15T14:56:11.863-0500 I JOURNAL [initandlisten] journal dir=/usr/lib/unifi-video/data/db/journal 2019-02-15T14:56:11.863-0500 I JOURNAL [initandlisten] recover : no journal files present, no recovery needed 2019-02-15T14:56:11.864-0500 I CONTROL [initandlisten] LogFile::synchronousAppend failed with 8192 bytes unwritten out of 8192 bytes; b=0x559a580de000 Invalid argument 2019-02-15T14:56:11.864-0500 I - [initandlisten] Fatal Assertion 13515 at src/mongo/db/storage/mmap_v1/logfile.cpp 248 2019-02-15T14:56:11.864-0500 I - [initandlisten] ***aborting after fassert() failure 2019-02-15T14:56:11.873-0500 F - [initandlisten] Got signal: 6 (Aborted). 0x559a548a27d1 0x559a548a19e9 0x559a548a1ecd 0x14f306a7a890 0x14f3066b5e97 0x14f3066b7801 0x559a53b369c5 0x559a54531370 0x559a54506084 0x559a54506675 0x559a5450d966 0x559a544ffb95 0x559a54475985 0x559a53b22dc3 0x559a53b42876 0x14f306698b97 0x559a53ba2a29

would it be possible to get the beta branch for the Video Controller brought up to 3.10.0 Beta 1? Thanks

fryfrog, thanks for the last update.. can you try updating the beta branch to the new 3.10 beta 1? https://community.ubnt.com/t5/UniFi-Video-Beta/UniFi-Video-3-10-0-Beta-1-Release/m-p/2513135#M19784

would it be possible to have someone update the beta branch to include the new unifi video 3.9.9-beta2? I tried in my clone of the branch but kept having issues i couldn't solve with the patch.

is it possible to get dig added to this container? or is there a way of pushing it in without cloning the github?