eds

They're marked as Finisar FTLX8571D3BCL SFP+SR/SW 10Gb/s 850nm Multimode SFP+ Transceiver Grade A I have four of them for the two cables. I could see myself getting one bad one, but four???

Hello, I purchased this router and the sfp port does not appear to be seeing my unraid server. I have the following setup: Monoprice LC LC multimode duplex fiber cable Finisar 850nm multimode sfp transceiver In the unraid server I have a Mellanox connect X-2 ethernet nic. Everything looks as if it should work, when the cable is connected I see no lights on the router or on the card. In addition, in swOS the sfp section says “no link”. Is there anything that looks wrong here?

Sorry about that, you're right. Just frustrated, I like this program, but each time I do an update I have to hold my breath that it does not break. I'm getting the classic "this site can't be reached. <IP ADDRESS> refused to connect" when click the webui launcher. The ip I have is 192.168.0.132:4040. I've attached a log. Any help would be appreciated. libresonic.log

God, I hate libresonic. Everytime I update this docker I have to hold my breath that it does not break. Unfortunatley I did an update and it broke. Anyone else using this docker with the same problem?

Ok. I am beginning to think this is connected to the vm. After rebooting a windows server vm, I lost connectivity for a short time (perhaps until the vm started back up). In the log I have these odd entries: A quick Google search and I came up with a few entries all dealing with vms including this one. I have a 750w power supply with two Intel® Xeon® CPU E5-2648L v3 @ 1.80GHz. I have two vms and 13 dockers running at all times. Average cpu load is about 40-50%. Could this be a hardware issue?

I'm not in the Apple environment any more so not sure I can help with this one.

Another odd, possibly related issue. I'm watching Plex and deleting a few files using krusader docker and all of a sudden I loose connectivity to the shares folder. From what I can see the user folder with all my shares is empty. Fortunately all the files and shares still live on a user0 drive. A reboot appears to have fixed the problem. I've attached the part of the log that appears relevant. Any help is, of course, appreciated. new 2.txt

Yes. Using maria db. This sounds like either a php issue or permissions issue. What are the error logs saying now?

For some reason I am having a chronic issue with loosing connectivity to unraid. The dashboard, the array, everything becomes inaccessible. The server is still working cause I can access the server management dashboard and I can see unraid is still running, but the network is down. This has happened three or four distinct times. Once is when I stopped the array. I restarted it and things were going fine. I then started my windows vm and a few minutes later the system became inaccessible. The second is when I wake the system from sleep. The system comes up fine then goes offline. Only way to get access is to restart the server. From a clean reboot, when I start the dockers and all vms everything works fine. Not sure where to look for solutions. Any help would be appreciated.

Resilio Sync. Sync, like nextcloud, will upload to any client systems with the app installed. But sync works well with large and small files (in case you shoot a video instead of picture). To display and share pics to folks, I use lychee and map it to the folder (dir) I upload my files on sync. Then I use the lychee function to upload from server. Note: using the upload from server function destroys the originals when the app grabs them.

I can't say for sure what your issue is because I used Nginx Proxy Manager to get nextcloud up and running. Perhaps you would have better luck using that? I tried to follow the instructions per spaceinvaderone's video and it did not work for me.

Great docker. Great app. Only two gripes. Unless I am missing it, no way to create subfolders. Unless I'm missing it, the only way to view pics is large thumbnail view. I don't see a way to list via a smaller thumbnail view or list view. Am I right?

Are you seeing the congratulations page when you check the domain name from outside your lan? If so, then forwarding is good. This one I am not so sure. If you are on a residential plan internet plan, port 80 might be being blocked by the isp (as was the case with me). Check to make sure port 80 is open by going to https://canyouseeme.org/ and checking 80. If it is open and you are forwarding the ddns correctly, letsencrypt should have no problems issuing a crt.

When I tried 443 I was getting the unraid dashboard. I decided to use my own custom 448. But for laughs and giggles, I'll try 444.

I can access Nextcloud when it has its own ip. It's when Nextcloud network type is bridge mode, I cannot access. Yeah -- I am baffled. Logs for each container tell me nothing. Very weird. Will keep looking around. May have to try another solution. This is the only docker that give me issues when in bridge mode.

Yes. I see nothing out of the ordinary. Plus, wouldn't that show up in the log and wouldn't the docker be unable to start if there were a port overlap/conflict?

In my experience it means letsencrypt cannot see the docker you are trying to secure from the wan side. Either the ddns setup is not correct or port 80 is being blocked.

Hello everyone, I'm kinda at my wits end here. Let me start by saying I have mariadb and nextcloud dockers installed and running. When I have both on their own ip, everything works fine. However I cannot access Nextcloud from outside my lan. So I put both in bridge mode. Now I have lost connectivity to Nextcloud. I click on the webui from the unraid dashboard and it terminates immediately with ERR_CONNECTION_REFUSED. I’ve done everything from deleting the nextcloud docker to starting from scratch and deleting the app folder and the docker image and reinstalling but nothing seems to work. From the logs on both dockers, I cannot see any issue. Not sure what to do. Any help would be much appreciated.

Has anyone gotten this to work with Nextcloud? I'm stuck since nextcloud seems to throw errors and cannot connect to my mysql container if on a bridge network. So I have to assign nextcloud its own ip address in order to work. But doing so causes gateway issues for this app.

@DJoss Thanks man, I finally got it working! For me, a few things that may help others: 1. This only works if the various containers are in bridge mode (which I think was previously discussed on this board, but I forgot). All my containers had their own ip addresses so I had to change each, stop and restart them. Remember once all containers using this app are in bridge mode, in proxy manager, the ip address is now unraid's ip (with different ports). 2. Also, its worth noting, you DO NOT have to port forward in your router to any of the containers. Only forward ports to this app as required and that's it. So I had to remove all the port forwards and ips for the various containers within my router. 3. My namecheap subdomain set up was right on. Cname subdomains for each app linked to the domain name seems to be work. No need to do a wild card. 4. In the apps, I made sure all containers did not reference ssl anywhere. 5. All destination ips in proxy manager were set to http (so http://unraidip:appport). 6. I knew I was on to something when, looking at the logs, lets encrypt would accurately send an crt. Still could not get my custom cert to work but beggers cannot be choosers. 7. One annoyance -- the proxy app times out when trying to secure an ssl certificate via lets encrypt. So it appears to fail, but when you cancel the function you are able to select the ssl cert. 8. Finally, once lets encrypt had the cert, I set each subdomain to force use the crt and it works. Great app!

No. I only see the error I've done some fiddling and got some progress. Putting the ssl issue aside for a moment... I was able to open port 80 on my modem which was surprisingly easy. So i port forwarded port 80 to the docker and I am able to see, from both vpn and my mobile device, the congratulations page of nginx. Nice! Now, I am using namecheap as my ddns (which works great with my asus router so why use duckdns which does not??). This could be where I am getting stuck. I read a few pages back when using your own domain name you need to create a subdomain using a cname record and have host: * and value: yourdomainname.com That wildcard now causes every subdomain to go to the congratulations page (i.e. couchpotato.yourdomainname.com,nzbget.yourdomainname.com, etc ). Is that a good thing? If I create an entry in nginx proxy manager and a cname host: couchpotato value: yourdomainname.com I get a "Bad Gateway" error when it type in couchpotato.yourdomainname.com. Then, i read elsewhere you do not need a cname, but an a record. So I also created an a record with host: couchpotato value: ip address of my router. Finally, I tried removing everything in namecheap except the cname wildcard entry (*.yourdomainname.com) and just adding an entry in proxy manager and that took me to a 502 bad gateway. Which of these is correct? It seems to me the last entry should be correct, but I get a 502 error page. What is that about? Info in ngnix seems straightforward so I cannot imagine there is a problem there. Thanks for your help!

This is a great docker and I am just getting started. I can access my server via http without issue. But I'm having issues using my custom ssl. I am getting err ssl version or cipher mismatch when i try to access the server via the secure port. Not sure what the problem is. Entering the ssl and key is simple. However I notice the fields do not change when I enter the location of the certificate and key (by that I mean, the js box does not populate with the location of crt and key such as c://documents/ssl/key.pem). Is that to be expected? When I add ssl it saves with the correct expiration date, but says the provider is "custom". Also, crt and key are pem encoded. Is there an issue with that? Thanks for your help.

Sorry to bump an old post, but I'm having the same issue. I don't know if this was ever resolved by OP, but I can't seem to figure out why my CentOS install cannot find a network controller. Very frustrating. Any help would be appreciated. Thanks.

I am seeing the same issue. Started after the most recent update. Did the force update thing, still didn't work. Have you found a solution? Any help appreciated. Logs attached. airsonic.log

Are you using dnns? Which one?