Hotsammysliz

So I spoke with some friends about this for help and there were two things happening at once here. first thing was that my dns records were having an issue. On my old domain host of Hover the dns records were setup as such and were working: TYPE HOST VALUE A arecord.domain.old PUBLIC.IP.IS.HERE CNAME cname.domain.old arecord So with that I set them up the same on my new domain host over at porkbun but like stated in my original post arecord.domain.new worked but cname.domain.new did not work. I learned that Hover was basically using shorthand in the DNS records CNAME value so although I entered 'arecord' and that worked what it was actually doing was using 'arecord.domain.old' as the value. After learning this I updated my DNS records on Porkbun accordingly and everything began working again. Just for more detail this is what they look like on Porkbun TYPE HOST VALUE A arecord.domain.new PUBLIC.IP.IS.HERE CNAME cname.domain.new arecord.domain.new As for the issue with port 80 I did indeed confirm with my ISP that port 80 is now blocked which explained why I could no longer use http validation and had to switch to dns. It was essentially a very simple fix but I hope this can help someone who may end up in a similar situation as mine!

So to get right to the issue I am not able to reach any of my CNAME subdomains going through SWAG but I can reach the "Welcome to SWAG Instance" going to my domains A record. To give a the full picture I'll detail everything about my situation. About a month ago my ISPs public IP changed. I didn't think anything of it, updated my domain records to match and everything continued to work. This past weekend I noticed I suddenly could not reach any of my services doing through the swag but I hadn't changed anything. I took a look at the logs of SWAG to see that I was unable to renew my http cert so chances are this issue was probably happening since the IP change but I did not notice since the cert had not expired yet. The issue I was getting with the swag certbot was stating something like "likely firewall problem" even though nothing had changed on my router. I tested ports to my public using 443 which was successful but 80 was not which lead me to believe that my ISP is now blocking port 80 since the IP change that happened a month ago but everything was working since the cert had not expired yet (I don't know if this is 100% correct so please let me know if that suspicion is wrong). Going off of that I researched and found that instead of using http cert in SWAG I had to use dns. My host service at the time was hover which I learned does not have support/api to use as a dns cert in SWAG so I looked into different hosts. I settled on porkbun as the pricing was good and it supported SWAG as well as my pfsense router for DDNS. Since I have to wait a week for the transfer of my old domain I bought a cheap new one in the meantime and copied all my records over to match. I updated the docker settings in SWAG to be dns cert with the new domain and changed the subdomains to wildcard and the new cert looks to be created and working. My issue now is that like I mentioned earlier I still cant get to any of my services at "cname.domain.new" but I can get to the A record public ip domain "arecord.domain.new". Specifically I can get to https://arecord.domain.new but I am not able to get to http:// of anything. I am not sure if that is the expected outcome now using the dns cert or not but just trying to provide any useful information. Since the domain is new I also tested the DNS propagation as well to just see if I was being impatient and all the records look to be pointing where they are supposed to as in "arecord.domain.new" points to my public ip and "cname.domain.new" points to "arecord" so I dont think it is a propagation problem. If anyone has any kind of insight to what I am missing it would be GREATLY appreciated. I've been banging my head against a wall trying to figure this out for like the last 18 hours straight.

I realize this is very late reply but I've been going through and testing my processes as well as completely rebuilding my offsite backup server so things are moving albeit slowly. But I was curious specifically about what you have loaded on your flash drives as bootable software. I'd love to just hear what your specific process looks like just for more ideas. Thanks for the help!

Just adding to this that the latest version is now just completely broken on install. Tried updating on my main Unraid and none of the solutions listed above work unfortunately. Also just as a sanity check tried installing this docker on a separate brand new Unraid server with no previous configurations and still no luck. Only working solution for me is sticking to version tag 69 by setting the repository property to: immybot/remotely:69. Hopefully something is fixed in the future.

Yes that makes! Thanks for clearing that up. So essentially I want to have a different backup method outside of duplicati that I can rely on to restore duplicati (along with the other docker apps) appdata config and then once that's been restored proceed with duplicati restoration. Thanks again for the help. I think I know how to move forward now!

Thanks for the info! So duplicati is running as a docker app on the unRAID server and I am backing up my docker apps, as in the appdata folder, through duplicati to a remote location. Is there a different way I should be backing up my docker apps? I think the part that confuses me a little in this process is the last 2 steps and maybe that's where my process needs to change. If I'm backing up all my data with duplicati how can I restore that duplicati data for itself before installing duplicati? Hopefully that question makes sense. Thanks again for the help.

Hello all! So I've been using Unraid now for about 3 years and have been loving it just recently upgraded to pro and about to setup another server remotely. I initially setup my 1st Unraid because i had a catastrophic server failure prior to. So now that I've got things all setup running well with Unraid I'm curious what the process would look like if I completely lost my server (i.e fire, flood, etc). I do currently have my flash backup running (I think that's something I setup through a SpaceInvader guide). Then those backups along with all other important data on my arrays is being backed up through duplicati to a remote S3 bucket. So if I had to get all new hardware, in this situation just assume exact same for drive and cache sizes, what would that process exactly look like? Should I be backing up the flash to something not related to my array and if so what and where do you folks do that with? How would I access and actually restore my duplicati backups if the machine I am backing up is gone? should I be making regular exports of my duplicati jobs as well and if so is there a way to schedule that. I've been burnt once so I am backing things up but I've never fully thought about the whole process to restore if i happen to lose everything at once. Hope these questions all make sense. Also not sure where this topic should be exactly since it's not really support or anything so please let me know if this should be moved or deleted and posted somewhere else. Thanks!