• Posts

  • Joined

  • Last visited

Everything posted by 2000gtacoma

  1. Fired up a trial of unraid on another desktop I had laying around. Connected perfectly to myservers. Must be something with my server causing issues. Any ideas on what to check? Rebuild flash drive? Took the trial flash I setup for testing, removed my original drive from my server, plugged in the trial drive and the myservers connected perfectly. Even used the same IP address and ports. So ruled out a router/port forwarding issue at this point. I'm guessing somewhere there is a file not quite right on my flash drive or maybe by chance something on the unraid end with my server? Just asking not bashing at all. I did rename this server at one point. Maybe that fubard something?
  2. Thanks I appreciate that. Anything I can check on my end? Also now just randomly saw a an error under my server name in unraid (where is usually says can not connect to mothership) graphql is offline. Did unraid-api restart and that goes back to can't connect.
  3. Played around some more. Both servers under myservers went away. Reinstalled myservers, signed back in, showed up under myservers as signed in but still not connecting to the mothership. Did the unraid-api restart, and I get this root@myserver ~# unraid-api restart Stopping unraid-api process... Process stopped! Starting unraid-api in "production" mode. Loading UPC API key... Emitting "add" event Emitting "replace" event Loading MyServers API key... No PID found in cache for unraid-api Loading state paths Daemonizing process. Daemonized successfully! Is the no pid found in cache for unraid-api normal?
  4. Just tried this. Opened web terminal stopped api. Deleted the file on the flashdrive. Reloaded GUI. I'm assuming UPC is the sign in for the my servers in the top right? Nothing there. Rebooted server still nothing in the top right. Removed the myservers plugin. Deleted the config\plugins\dynamix.my.servers folder. Reinstalled myservers plugin. Signed in. Check access under management access. Get the green check mark. Still get the cannot connect to mothership. Still showing 2 servers under my myservers account. Thoughts?
  5. Any updates? Mine is still not connecting to the mothership? No rush just curious.
  6. Thank you. If you need any other data, info, diagnostics, if I can help please feel free to reach out.
  7. Yep did that. Mentioned that in my original post. When I run the unraid-api restart I see the status change to disconnected from unraid api then back to can't connect to mothership. When I originally installed this the first time the api restart worked perfect. Edit: Here is what I get when unraid-api restart is typed root@myserver:~# unraid-api restart Stopping unraid-api process... Process stopped! Starting unraid-api in "production" mode. Loading UPC API key... Emitting "add" event Emitting "replace" event Loading MyServers API key... No PID found in cache for unraid-api Loading state paths Daemonizing process. Daemonized successfully!
  8. Hey folks had the myservers plugin setup and running for a while. It stopped working. Uninstalled and reinstalled. Says not connected to the mothership. Cert provisioned, port forwarded in router, I can click the check button under management access and it says your server can be reached. Tried opening a terminal and typing unraid-api restart. Didn't make a difference. Any suggestions? Edit: Something weird I noticed is I can turn on flash backup and it will update on the myservers page. Also I am on the latest version. Its almost like maybe the myservers page is confused from the time I was running trial vs when I purchased my pro key. I'm showing 2 servers under myservers.
  9. Hey folks, So I finally figured out where my hiccup was on swag. jonathonm commented on another post and suggested in was a porting issue. Turns out that was correct. So in my centurylink modem. I can port forward just fine, but I can not translate for example external 443 to internal 1443. What I did to figure this out is changed the ports that unraid uses. Once I did that I could port forward 443 in my modem/router and swag would connect. I could still access unraid at my internal ip 192.168.1.x:180 which is the "new" port I gave it. So I can not translate ports (terminology?) but I can forward. Are there any other options besides changing the unraid ports and letting swag have the 443 ports? I had thought about purchasing a router and bridging the modem.
  10. So I created the proxynet as suggested. The swag docker has ip of 172.18.0.x and the points to the server's ip of 192.168 on port 1443 and 180. I forwarded ports 1443 and 180 as well as 443 and 80 in my router. I can only port forward to ip addresses in my router. I can open a console from the swag container and ping and it pings fine. I can ping my server as well. I even went as far as to disable the entire ipv4 firewall temporarily on my router and still didn't work. I am on centurylink and use the modem/router from them. I don't really see any option to say "translate" port 443 external to port 1443 internal.
  11. First time posting here guys. Just started playing with unraid. So far I like it. Just learning more how to use it. First I was trying to follow a couple online videos about how to setup nextcloud with a reverse proxy using duckdns and swag. I think I have the duckdns part setup fine. (I also setup openvpn-as and that works fine.) However I keep getting errors when starting swag up in the log file. I setup swag using a proxynet as described by spaceinvader on youtube. I have swag pointed to my duckdns subdomain. I setup the port forwards in my router. (spaceinvader used 180,1443. Also forwarded another port for openvpn-as. Confirmed that doesn't work if not forwarded. Works fine forwarded.) I am getting certbot failed to authenticate some domains error. Any help would be much appreciated. I've done nothing but read and recheck what I've done the past couple days. Ultimately I want nextcloud as my personal gdrive if you will. Below I have the log file (I think), the x's are personal things I edited out really quick. Using Let's Encrypt as the cert provider SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d xxxxxx.duckdns.org E-mail address entered: xxxxxxx@gmail.com http validation is selected Generating new certificate Requesting a certificate for xxxxx.duckdns.org Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems: Domain: xxxxx.duckdns.org Type: connection Detail: Fetching http://xxxxxx.duckdns.org/.well-known/acme-challenge/Hwgvot2j9PxOGJvd5RFZ0mNG2zyS8zMbRPp8OZ91lgY: Timeout during connect (likely firewall problem) Hint: The Certificate Authority couldn't externally verify that the standalone plugin completed the required http-01 challenges. Ensure the plugin is configured correctly and that the changes it makes are accessible from the internet. Saving debug log to /var/log/letsencrypt/letsencrypt.log 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