Can't synchronize TV shows folder from different source. I keep getting the "operation has failed"

So I am having an infuriating issue where I cannot syncrhonize my TV shows folder from another source. It just says "operation failed." Does anyone know how to fix this? What happened is I upgraded my router so the IP range changed. The movies folder synchronizes from the previous source just fine, but not the TV shows. It just flags this error.

Does anyone know how to fix this?

I am on the latest beta firmware for the z9x (not pro)

 

Just an update: If I change my IP range back to what it was, everything is fine. But I'd like to know how to fix this for if/when I change my IP range.

 

I have had the same issue. Folder containing movies only syncs fine. Folder with TV shows generates error.

 

Ah ok. Yea that stinks though. Basically means I'm stuck with this IP range, unless I want to have to re-do the entire TV Shows library....hope there is some sort of workaround.

 

Doesn't stink at all - just maintain your network properly.

The very first thing I would do if I change my router is to make sure the subnet is the same as the old one. Schoolboy error if you don't.

I'd then make sure the DHCP range is the same (getting slightly more technical) as the old router and any MAC DHCP allocations (I only use them for Squeezebox clients) are the same.

Then all the 120 or so clients on my network wouldn't even notice.

Simple.

 

Right, I get you, and it works fine now that I changed it to the old range. But I want to be able to change my network range. It's for another thing I'm doing. So is there no way to do this without having to rebuild the library?

 

Why?

 

I use a pihole and pivpn. I'm trying to see what happens if I were to be connected to say a friend's wifi that had the same IP range as I have at home. Then pivpn probably won't work (maybe?). So I figured I'd just change my IP range to avoid conflicts.

 

Different network entirely, there won't be any conflicts because there's nothing to conflict with.

Most home networks are on 192.168.0.x some maybe 192.0.x.x and some others maybe 10.0.0.x if they're being clever (I use 192.168.0.x for my main network and 10.0.0.x for my guest network) but if you move to another network (your friend's for example) it makes not a one jot of a difference to how yours is configured.

Keep it simple - choose a subnet and stick to it, then you don't need to worry about any client configuration down the line.

 

You're right of course - if TV series don't synchronise from a different source, then that's a bit pants, but in this case, there's really no need to use that - sledge hammer/nut kind of thing...

 

Apologies if this is obvious. So for example, let's pretend my router IP is 192.168.1.1. And then I'm at my friend's house, who also has 192.168.1.1 as his router IP. If I'm connected to Wireguard (on mobile) back to pivpn at home, you're saying there is no conflict? If I were to type 192.168.1.1 into the URL bar, would I get my router login page, or my friend's whose network I'm on?

 

You'd get his login - 192.168.x.x. is reserved for local networks, same as 10.0.x.x.

If you want your login you'd have to use your external IP address and have a firewall rule to allow the traffic through on port 80.

 

Thanks. If we have the same router IP, would I still be able to get a connection back home? In other words, does Wireguard have a way to differentiate that my network is the correct one? Apologies if this is networking 101. I was told by a few people elsewhere that there would be a conflict.

 

192.168.1.1 would be his router address on his network and your router address on your network - as I say, these are reserved subnets for local addresses only so only relate to the local area network on which the devices reside - these addresses have no relevance to the wide area network (internet).

 

Thanks. Appreciate the information as always! Do we know though why the zidoo flags that error? Is it fixable? Assuming not since the Z9x (OG) is pretty old at this point.

 

Interesting response.

In my case, I changed ISP's and the router they gave my had a different subnet than my old one. It was locked down and could not be changed to match. One could argue that this was an extremely bad policy and I would not disagree. But it was what it was and I had to rebuild my TV shows from scratch.

I could also see a situation where one would desire to move some files from one NAS to another existing NAS on their network. Changing the IP on the 2 NAS units may not be practical.

In any event, it appears to me there is a bug here that prevents sync of TV shows for some reason.

 

Must admit I've never seen a router locked down so that you can't change the subnet - that's kind of the basics and could be required in any installation.

Anyway, it's kind of academic - I just tested it and "Synchronise data from other source" is working here.

I just scanned in a bunch of TV series, made sure all the matches and artwork were correct. Then I moved the lot so that source became "Invalid". Then added the new source and synchronised - no problem.

Tried this on a 1619DR (v6.4.65) and a 1619BPD (v1.0.86) and it worked on both so I'd chalk this up to finger trouble.

 

Weird. I am on the Zidoo Z9X on 6.4.65, and it gives me the error. I wonder what causes it...

 

I have a uhd3000 with same Firmware. I copied all to a bigger USB disk and TV Show sync does also not work, no Problems with the movies.

 

Yes, I was quite surprised at the limitation of that router. (It has since been replaced)

I have a Z9X (6.4.65 firmware currently) and am very pleased with it. I have 2 sources, a movie source and a TV show source. When I purchased my first NAS (about 1.5 years ago) I used the sync function to move my library over and it worked perfectly. Then I had the infamous router issue. At that point the sync function worked fine for the movie sources, but failed on the TV show source. (Not sure, but it may have coincided with the release of the firmware that supported metadata refresh).

For grins, tried it last night. Still get error for TV Shows. Perhaps some difference in the database structure?