glave

Looks like AWS has a bad route. 54.240.229.185 is the last hop I can hit before it dead ends.

Yea, it resolves, but I appear to be unable to connect to or ping any of the ips. Name: us-east-1-elbdefau-1nlhaqqbnj2z8-140214243.us-east-1.elb.amazonaws.com Addresses: 52.86.8.163 34.232.230.241 52.205.36.130 Aliases: hub.docker.com elb-default.us-east-1.aws.dckr.io

I can't pull the image down. Is the address still correct? TOTAL DATA PULLED: 0 B

I'm trying to replace the Limetech LE cert with my own, which is a wildcard. In doing so, unraid redirects my browser to https://%2A.mydomain.com. Is there a way to stop the redirect or at least correct it?

Nah... Just make a companion template for elasticsearch also! 😉

Is there an existing elasticsearch or redis container in community apps? I didn't see both of them and just wondering if they need to be created by hand first.

The WebGUI parameter isn't respecting that I changed it from the default. I changed it from 8080 to 8082, but when I launch WebGUI from the docker icon it still takes me to 8080.

I'm assuming it would be a good idea to ensure that if I'm allowing these custom networks to route, that I should not have a duplicate network between the two unraid servers?

That was such an obvious answer.... 😣

If I've created a custom network on my primary unraid server, how can I access containers on that network from a 2nd unraid server, or even my normal network?

I found it in the logs, but not sure why it's happening. I'm getting the error that the remote server is offline and the share cannot be mounted. That's odd because I can see in the logs that the network is definitely up, in fact a few seconds after the errors, I can see ntpd messages from it syncing. I did a few reboot tests and the results seem consistent as well, it just doesn't make much sense. Is it possible to maybe delay the mount a little longer, or possible mount it from userscripts instead?

I'm having a small issue with NFS shares. I have two unraid servers, one has several shares via NFS and I'm trying to use unassigned devices on the 2nd server to mount those shares. Mounting works perfectly fine, but automounting does not. On the 2nd server, when it boots the array starts, but the NFS shares never get automounted. If I click mount, they mount without any issue at all. Is there a log I could look for to see if it attempted an automount and got an error somewhere? Something I'm missing?

It's not something that comes up very often, but would it be possible to change the font size of the files being edited, or maybe add a horizontal scroll bar instead of doing a line wrap?

Two year old drive red balled on me. I'm guessing she's really dead, but this is what logs looked like: May 7 13:50:00 arcade kernel: sd 8:0:0:0: [sdk] tag#1 CDB: opcode=0x88 88 00 00 00 00 00 57 54 2b 10 00 00 00 08 00 00 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 Sense Key : 0x2 [current] May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 ASC=0x4 ASCQ=0x0 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 57 54 2b 10 00 00 00 08 00 00 May 7 13:50:04 arcade kernel: print_req_error: I/O error, dev sdk, sector 1465133840 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 Sense Key : 0x2 [current] May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 ASC=0x4 ASCQ=0x0 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 CDB: opcode=0x88 88 00 00 00 00 02 0b f8 f5 50 00 00 00 08 00 00 May 7 13:50:04 arcade kernel: print_req_error: I/O error, dev sdk, sector 8790799696 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 Sense Key : 0x2 [current] May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 ASC=0x4 ASCQ=0x0 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 May 7 13:50:04 arcade kernel: print_req_error: I/O error, dev sdk, sector 0 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 Sense Key : 0x2 [current] May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 ASC=0x4 ASCQ=0x0 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 02 0b f8 f5 58 00 00 00 10 00 00 May 7 13:50:04 arcade kernel: print_req_error: I/O error, dev sdk, sector 8790799704 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 Sense Key : 0x2 [current] May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 ASC=0x4 ASCQ=0x0 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 ae bc 80 c0 00 00 00 08 00 00 May 7 13:50:04 arcade kernel: print_req_error: I/O error, dev sdk, sector 2931589312 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#1 Sense Key : 0x2 [current] May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#1 ASC=0x4 ASCQ=0x0 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#1 CDB: opcode=0x8a 8a 00 00 00 00 02 0b f8 f5 50 00 00 00 08 00 00 May 7 13:50:04 arcade kernel: print_req_error: I/O error, dev sdk, sector 8790799696 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#4 Sense Key : 0x2 [current] May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#4 ASC=0x4 ASCQ=0x0 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#4 CDB: opcode=0x8a 8a 00 00 00 00 00 57 54 2b 10 00 00 00 08 00 00 May 7 13:50:04 arcade kernel: print_req_error: I/O error, dev sdk, sector 1465133840 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#5 Sense Key : 0x2 [current] May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#5 ASC=0x4 ASCQ=0x0 May 7 13:50:04 arcade kernel: sd 8:0:0:0: [sdk] tag#5 CDB: opcode=0x8a 8a 08 00 00 00 00 ae bc 80 c0 00 00 00 08 00 00 May 7 13:50:04 arcade kernel: print_req_error: I/O error, dev sdk, sector 2931589312 May 7 13:50:43 arcade kernel: sd 8:0:0:0: [sdk] Synchronizing SCSI cache May 7 13:50:43 arcade kernel: sd 8:0:0:0: [sdk] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00

DOH! I actually had that already installed too.....

What's the possibility of adding the ability to edit the go script from the scripts page? It'd be a nice one stop shop for making adjustments then!

Ah yes! That got it back on track perfectly. Thank you for finding that!

Definitely not a dry run, but I am using custom flags: -avRXO --partial

Yup, 6.3.5! Switching browsers makes the display change from 'Waiting' to '0.00% done ~ 0s left (0.00 MB/s)' but it never changes from that. Looking in the logs, I see no lines at all with "Current progress" in them.

What determines the stats information? I've noticed recently that stats never actually collect, I just have a perpetual "Waiting to collect stats". I'm currently moving some stuff that has been running for over an hour, moved MANY things successfully, but still hasn't generated stats.

Quoting- Chrome isn't liking it, Firefox is... From the Docker tab....HA! The number of dockers I have, along with my web browser sizing, everything lined up perfectly so it was all on the page and I didn't notice I can actually scroll further down and TADA- there's the autostart manager. I switched back to tabbed views now, so I hopefully won't be duped by my own ignorance again on that one.

(Sorry, I'm not sure why I can't get the quote function working in the new forum) " Never thought about it, since while the plugins tab does have the ability to take you to a plugin's settings, no one expects you to ever actually use that feature (because its so slow)" - Squid Wait, that's not how you access Docker Autostart (plugins page)? Where do you normally access it from?

Squid- I actually forgot about plugins that 'embed' into another page like that. I think for those, that makes perfect sense, as if the plugin is enhancing a particular item, it belongs in that page. Perfect example is own of your plugins, Docker Autostart I access the page by going to Plugins, when I click the plugin it takes me to it's page, but now my section is showing Settings. Would a plugin like this make more sense adding it's enhancements to the default Docker settings page? (Settings > Docker) I completely realize getting accustomed to where different plugins 'reside' makes this a complete non-issue. I'm just thinking that when the server has been running very well for a period of time, well, out of sight- out of mind, and it's easy to lose track.

I'm not sure if there's an underlying pattern that I haven't seen yet, so I made this post in General Support rather than Feature Request... Is there a rhyme or reason to where a plugin ends up within the webpage? Could we talk about a standard for that if there is not? For example, sometimes you access their components via the Settings section(that never made sense to me), sometimes you do it from the Plugins section (I never like them here do to the slowdown of refresh EVERY TIME the page is accessed), seldom you can find it in the Tools section (made the most sense to me). Lots of plugins I use are not frequently touched, and over time of installing more and more, it has become a bit of a hide and seek game sometimes when I needed to use one that I haven't revisited in a while. Is this an issue for others or is it just me (probably just me....)

I'm as guilty as a lot of other plugin guys here. Functionality first. Help files whenever we get around to it. (truth be told I never even thought about it) After work it'll get done. If you're thinking of putting in full help on how to build a crontab, there's TONS of 'generators' out there that you could just borrow a bit of design from instead. http://corntab.com/ has a pretty functional way of doing it that has most of the flexibility and basics that cron can do.