altyne

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by altyne

  1. @Squid I know the reason. Just now we have experience a brownout; it happens only a few seconds. Just now parity checking is running. During that time around 08:22:21AM , I didn't know we have a power outage and I was sleeping. Thanks to all. I need to protect my server with UPS since occasionally brownout occurs in my place.
  2. I didn't shutdown my machine. Its running 24x7. That's the reason the parity check was triggered?
  3. @itimpi it is safe this to modify this file directly - /etc/cron.d/root?
  4. @itimpi I have attached the diagnostics - nightowl-diagnostics-20220101-1422.zip this is the content of cron: # Generated parity check schedule: 30 2 1 12 * /usr/local/sbin/mdcmd check &> /dev/null || :
  5. I set to yearly. I am expecting this should executed in year but it executes now. Before this, I used monthly or even disable still randomly it executes itself. Scheduled parity check: yearly (latest) Day of the week: --- Day of the month: First day Time of the day: 2:30 Month of the year: December Write corrections to parity disk: Yes See the history: 2021-12-20, 15:33:45 16 hr, 41 min, 43 sec 133.1 MB/s OK 0 2021-10-23, 15:30:27 16 hr, 33 min, 20 sec 134.3 MB/s OK 0 2021-10-10, 16:21:52 16 hr, 21 min, 51 sec 135.8 MB/s OK 0 2021-09-10, 16:18:48 16 hr, 18 min, 47 sec 136.3 MB/s OK 0 2021-08-08, 13:42:12 16 hr, 17 min, 50 sec 136.4 MB/s OK 0 Diagnostics attached. nightowl-diagnostics-20220101-1422.zip
  6. It working for me right now, what I did; was disabled the firewall settings built in in my router and upnp options. Well, looks like this thread is like a rant and nobody cares to read for 228 pages long. what I bummer. What I observed from SpaceInvaderOne guides are still good but most are outdated unless he updated in the comment section. For others content, you can follow but you should be cautious because settings will likely not compatible with latest version. Some tips and gotcha I'd observed, you can get the instruction inside cnf/config files in comments section. And also read author documentations/wiki guides on how to configure. Unraid server (particularly docker) just present the configuration in the screen and eventually submitted into command line. You can read author's guide or clicking the question mark in the top right screen below your username; to see some valid values and tips.
  7. I managed to installed the SSL via cloudflare. However, my router blocks port 80 and showing the router web admin page? Did ignore port forwarding ? internet -> router (port 80 forwarded -> unraid server port 192.168.x.x:180 -> nextcloud : 80) internet -> router (blocks here returns web admin page from router)?
  8. i resolve my issue is port used. However i have issue again: Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems: Domain: cloud.myowndomain.com Type: connection Detail: Fetching http://cloud.myowndomain.com/.well-known/acme-challenge/MW0vkuKtEVdJrtPHQhH-_BqvajZK31sTq18SZuk2qug: Timeout during connect (likely firewall problem) Hint: The Certificate Authority failed to download the challenge files from the temporary standalone webserver started by Certbot on port 80. Ensure that the listed domains point to this machine and that it can accept inbound connections from the internet. Some challenges have failed. Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container
  9. Need help. I have an error while intalling the docker swag: I cannot see the logs since after installation and running the docket setup remove the image. But I see the commands generated: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='swag' --net='proxynet' -e TZ="Europe/Madrid" -e HOST_OS="Unraid" -e 'EMAIL'='test@gmail.com' -e 'URL'='myownadomain.com' -e 'SUBDOMAINS'='cloud' -e 'ONLY_SUBDOMAINS'='false' -e 'VALIDATION'='http' -e 'DNSPLUGIN'='' -e 'EXTRA_DOMAINS'='' -e 'STAGING'='false' -e 'DUCKDNSTOKEN'='' -e 'PROPAGATION'='' -e 'PUID'='99' -e 'PGID'='100' -p '180:80/tcp' -p '1443:443/tcp' -v '/mnt/user/appdata/swag':'/config':'rw' --cap-add=NET_ADMIN 'linuxserver/swag' 8234a2c63b968ed9a9ee04b5d0f10e93352e6424393d2d9531ce27b587916872