urbanracer34

How was this solved?

Talked to Alexis (Staff) on discord. This is an issue on Let's encrypt's end.

So I have another problem. I'm getting these errors in the logs for the last couple days and I think it has to do with let's encrypt. It's sometimes twice a hour. Here's one of the errors,: Mar 2 08:18:51 GIBSON nginx: 2022/03/02 08:18:51 [error] 9544#9544: OCSP responder timed out (110: Connection timed out) while requesting certificate status, responder: r3.o.lencr.org, peer: 142.165.4.40:80, certificate: "/etc/ssl/certs/unraid_bundle.pem" The IP listed is not my IP. Diagnostics attached. Is this to do with My Servers? gibson-diagnostics-20220302-0827.zip

So now I have another problem... SIGH I tried accessing some photos on my server from my gaming PC on windows 10. I get nginx errors in the logs. 192.168.1.110 is the gaming PC. When I access the photos on Windows 10 using the built in photos app, the nginx errors go crazy, and the application gives an error message, which I have attached in a screenshot below. It seems as if accessing the images using the recent files section of file explorer causes the errors (the file explorer states "path" and then has the location of the file in question.) When I actually sign in to my server from my gaming PC and try to access the files after doing so, there is no trouble and no errors with the files. My mac computer doesn't break a sweat. It loads the photos no problem with no errors in the logs. gibson-diagnostics-20220207-1043.zip

So they are scanning the web and have been marked as abusive. Is this log entry a one time fluke or should I change some settings.

Yes my server is open to the internet on a few ports. I have "my servers" open on one port (which is I think the problem as the port is 443 but it is only accessible though another port, not direct.) The only others are plex and rtorrent.

Good morning, I was looking at my server's logs this morning and I think I found someone was trying to break in. Can someone give me some help interpreting this? Should I be worried? Diagnostics attached. gibson-diagnostics-20220206-1015.zip

Any insight? I know I've made numerous edits to the above post.

I have unraid version 6.9.2. I have 2 macs, macbook pro on Big Sur and mac mini on Catalina. Both are backed up to my server on the same share. I tried a test. I got the MacBook Pro (SUR) to back up to the share, Starting at 9 AM local time. It is unbelievably slow. It had to back up over 600MB of data and it has 200MB more to back up. 50MB out of 200MB so far done. It is still ongoing. Did I mention this is hardwired? Now it has restarted backing up the 200MB. It is backing up the 200MB for the 3rd time. Rebooted Macbook, hopefully that will fix it. Backing up 500MB now. Now it says "Cleaning up" after 1.5 hours progress. Going to try to restart server. I'll get diag first. Got diag from before restart, waiting to see what it will back up. This is over 7 hours troubleshooting so far. 220MB going to be backed up. Uploaded diag from before restart. I'm giving up on this for today (Sunday) until I get further info. I hopped onto the mac mini (CAT) and told it to back up to the share, 100MB. It was done in 15 minutes. Also hardwired. What is going on? gibson-diagnostics-20220109-1615.zip

I upgraded to the latest pull and part of my interface is garbled where it states what versions are running. I would post a screenshot but it appears my public IP is in the mess as well.

Where can I find the report again? I found it. It was temp related. Closing thread.

So I've run into an issue. I haven't touched my server physically in a long time, and I have it do an array health report every 6 hours to send to my phone. Most of the time it says PASS, but sometimes it says FAIL. There doesn't seem to be a cause for it. I don't see any error counts on the front page. I am at a loss. Can someone help? gibson-diagnostics-20210627-0951.zip

Perhaps my memory is wrong then. Thanks for the clarification.

Running 6.9.2. I noticed that when I close my browser window (Chrome) open another one and go to my server, I need to relog into the server. Also tested with firefox. As far as I know, this is not intended behaviour. This just started up today if my memory is correct. I have attached diagnostics. gibson-diagnostics-20210605-1034.zip

I tried connecting with the guest account and it said "Operation could not be completed. Invalid argument"

I am trying to access my server using the files app on my iPhone (I assume via SMB) It says 0 items and is read only. I've tried even reentering my credentials to no effect. Could the My Server's plugin be at fault due to the DNS rebinding?

Just thought people should know about this: https://www.nicehash.com/blog/post/stop-using-phoenix-miner-immediately

From Linuxserver's Github: https://github.com/linuxserver/docker-rutorrent/issues/188 We will continue with dropping support with this container in due course. We will be recommending current users to migrate to CrazyMax's rutorent cotainer: https://github.com/crazy-max/docker-rtorrent-rutorrent/ The question is how to migrate when the developer doesn't support unraid? Conversation I had with the person who makes this container: https://github.com/crazy-max/docker-rtorrent-rutorrent/issues/59 https://github.com/crazy-max/docker-nextcloud/issues/20#issuecomment-506553956

JUST AN FYI: THIS IMAGE COULD BE REMOVED AT ANY TIME. HERE'S MORE INFO: https://github.com/linuxserver/docker-rutorrent/issues/188

Hello, I am having an issue regarding my instance of rutorrent. After updating to 6.9.1 my Docker for rutorrent has been hovering around 8% CPU usage consistently. I am using linuxserver/rutorrent:2fce6c70-ls25 for compatibility for some sites I use. A run of the "top" command is attached in an image

That worked. Thanks!

Not sure if this is the best place for this, but my server says https://registry.hub.docker.com/u/binhex/arch-krusader/ is no longer available. Looks like it fixed itself for the time being. https://registry.hub.docker.com/u/binhex/arch-krusader/ is completely blank. What is going on?

Issue appears to be fixed as of latest update.

Same here.

Awesome! Thanks for the info!