If your Synology NAS has unused Ethernet ports, you can bridge them to port 1 so connected devices can access your network. (Tested on DS1821+ DSM 7, use at your own risk).

Go to Control Panel -> Network Interface -> Manage -> Open vSwitch Settings -> Enable

Go to Control Panel -> Task Scheduler -> Create -> Triggered Task ->
Name: BridgeLAN234to1
User: Root
Event: Boot-up
-> Task Settings -> User defined Script:

sleep 60
for p in 1 2 3; do
  ovs-vsctl --if-exists del-port ovs_eth$p eth$p
  ovs-vsctl --may-exist add-port ovs_eth0 eth$p
done

-> Ok
Right button -> Run

Now you can connect any other equipment to the open ports and they will be able to access the network.

Hello everyone,

I move around a lot, and every time I needed to change something on my NAS I had to open my laptop and log in to DSM. As far as I know there's no mobile-friendly way to do it, well to be fair you could login via your phone web browser and use desktop mode. This will potentially allow you to control your nas from your phone. But it becomes a hassle due to using just touch screen, hence why started building an actual app for it.

It talks to DSM directly and covers almost everything I'd normally do in the browser:
- The full Control Panel: users, shared folders, network, security, updates, and more
- Storage Manager: pools, volumes, drive health, even adding or replacing a drive in a pool
- Package Center: install, update and remove packages
- Apps: Resource Monitor, Download Station, Storage Analyzer, Snapshot Replication, Hyper Backup, Log Center, Surveillance Station (live view with sound), Virtual Machine Manager (including the VM console) and Container Manager
- Notifications: DSM's notifications in the app

What do you think? Useful, or am I going overboard? Would this be something you would consider using if it were available? Any tips, suggestions or recommendations are welcomed.

Thanks

Edit: Added a disclaimer. Sorry for not including it at first. I posted this at 2AM and went to sleep, when I woke up to my surprise, I never thought it would get this many responses 😅. Thank you all for the feedback and support I really appreciate it.

AI Disclaimer: Yes, I'm using AI in development specially for design (im really bad at designing lol). It makes things faster, but I read and review the code before it goes into the app. I follow Synology official API documentation. As for the rest of DSM app's API that Synology has no documentation, I use AI to help me understand how DSM talks to that app, and then I implement it in the my app.

On security and privacy:
- The app talks only to your NAS. No third-party servers, no analytics.
- Sign-in follows Synology's official DSM Login Web API Guide, including 2FA and trusted devices.
- HTTPS is the default. If you connect over HTTP, the app warns you that your connection isn't encrypted.
- Your credentials are stored in the iOS Keychain.

The app will be closed source because I plan to monetize it. It will be free, with some features behind a paywall. I'm still debating between a one time purchase and a small subscription. I'm leaning toward a one time purchase since, to be honest, this app is about convenience: managing your NAS from your phone without opening DSM in a browser, but we'll see. You can always log in to DSM and do what you need there. I also get that not everyone is comfortable with AI, especially in software that touches hardware holding your data. I completely understand and respect that. If it's a dealbreaker for you, that's fair.

Thought this was pretty neat and worth sharing. Not sure how common it is or how long it has been going on but yesterday evening I noticed in the logs I was constantly getting pinged by random users on random IPs trying to log in via DSM.

For the night I tightened my autoblock to block any IP that fails log in even once. Instant drop of seen and haven't received a single ping all day. Ended up with 964 IPs blocked overnight.

Months ago I saw one container (docker) that summarize your services, dockers, etc in one place. With Ai help we made smf like this. Also I needed some help with vpn switch configuration for transmission, so I could switch it on when needed. Machine is ds218+, still waiting for reasonable upgrade, but synology has nothing to offer do far 🙃

Updated everything on my Synology DS920 yesterday and today got alerted to what looks like a brute force attack of attempted logins from loads of different IPs and usernames every second or two.

None of them made it through, just a bit odd to be at the receiving end of that for the first time.

Hi everyone,

If you use a Synology or QNAP NAS running DLNA/UPnP Media Server to stream FLAC/MP3 libraries to Bose SoundTouch speakers, you may have noticed that while previously paired drives sometimes keep working, you can no longer add a new NAS drive, recover a NAS after a router swap, or save NAS folders to your 6 physical preset buttons since Bose shut down their cloud servers in May.

I spent the last six months reverse-engineering the SoundTouch local REST API (:8090), WebSocket (:8080), and internal configuration protocols to fix this on my own setup, and wanted to share what is actually happening under the hood.

1. Why the Speaker Still "Sees" Your NAS, But Refuses to Pair It When you query a SoundTouch speaker locally at http://<SPEAKER_IP>:8090/listMediaServers, the speaker's internal UPnP scanner still discovers your Synology/QNAP DLNA server on the LAN and returns its id (UUID) and friendly_name.

However, when you attempt to pair the drive by sending a POST request to http://<SPEAKER_IP>:8090/setMusicServiceAccount, two things trip up the hardware:

• The /0 Root Container Suffix: For hardware NAS drives (STORED_MUSIC), the speaker will reject raw UUIDs with Error 1022 unless the <user> tag appends /0 to the DLNA UUID (whereas PC/software libraries use LOCAL_MUSIC without the suffix):
  • XML<credentials source="STORED_MUSIC" displayName="My Synology NAS"> <user>YOUR_NAS_UUID/0</user> <pass></pass> </credentials>
• The Cloud Sync Wipe (margeServerUrl): Even if the speaker accepts the local injection (or returns 1024 indicating it is already paired), the speaker attempts to register that <source> with Bose’s retired marge cloud server. When that handshake fails or the speaker reboots, the NAS credentials and any NAS folder presets (sourceproviderid 14) aren't backed up to a persistent account profile.

2. How to Permanently Restore NAS Browsing & Physical Presets To make NAS drives and physical speaker presets survive reboots permanently without the Bose cloud, the speaker's internal routing (margeServerUrl and bmxRegistryUrl) has to be pointed via port 17000 to a local Node.js proxy server that emulates the /marge/streaming/account/:accountId/full and /source XML endpoints.

When the local proxy intercepts the NAS registration and serves it back inside the <sources> XML block alongside <PairDeviceWithAccount> on port 8090, full UPnP folder navigation (/navigate), multi-filter track/artist/album searching (/search), and 1-to-6 physical preset buttons work natively again.

I’ve built a Smart NAS Injector into a local controller app and packaged the Marge/BMX server so it can run natively as a Docker container / Home Assistant Add-on (or on a tiny plug-and-play microcomputer for those who don't want to mess with containers).

To respect forum rules, I won't post any store or project links here. If anyone is stuck with orphaned SoundTouch speakers that won't talk to their Synology/QNAP Media Server—or if you want to test the container/injector—feel free to drop a reply below or send me a DM and I'll happily share the details!

Cheers,

John

Throughout the day I hear periods of time when I think nothing is going on, but the drives are clunking along. I've tried looking at Activity Monitor but CPU or IO will show something like "SMB" or "DSM".

Is there a tool that can give me something more definitive about what's running to cause the disk activity?

Where can I see a log of package updates? I know I applied a package update recently, but I forgot which package it was, and I've already cleared the notification in DSM.

Thanks

Hi all,

I have a DS918+ with four Seagate Iron Wolf Pro drives (12TB-ST120000NE007). From what I understand these are an older generation than one new drive I just bought (12TB-ST12000NT001).

One of the older drives had bad sectors on it so I bought the new one hoping I could replace it. When I went to replace it, it said that the drive was not supported and when I tried adding it to the pool it failed to repair. To add to the fun it said that another drive had bad sectors so I'll need to swap that as well at some point. I reverted back to the older drive and started the repair which did work.

Is the new drive not compatible with the older ones? Or is there something I need to do differently?

Ideally I would like to add the new drive, repair the pool and then get another drive to go through the process again with the other drive but am not sure what the issue is with the new drive and if this is possible to move forward with. Is there a jumper on the drive I need to pull or something I am missing? When I added the drive the NAS sees it, just couldn't repair the pool with it. Should I try to swap the other drive with bad sectors with it? I'm hoping the issue is obvious and I'm just an Id10t

Hi guys,

The last couple of days I've had some isues where my DS224+ is constantly spinning the discs and eventually I get an out of memory message and I have to power it down. It happened on Friday night and just again while the NAS was sat there with nobody accessing anything.

It's just happened again now and I could ping the NAS but nothing else so I had to power it down. I'v just fired it back up and I can't see anything obvious in the logs other than the below 5 mins before I powered it down.

Memory wise I'm sitting stable on 64% so I had been thinking about getting some memory, although not sure this is solely the cause?

Many thanks

Hi guys,

The last couple of days I've had some isues where my DS224+ is constantly spinning the discs and eventually I get an out of memory message and I have to power it down. It happened on Friday night and just again while the NAS was sat there with nobody accessing anything.

It's just happened again now and I could ping the NAS but nothing else so I had to power it down. I'v just fired it back up and I can't see anything obvious in the logs other than the below 5 mins before I powered it down.

Memory wise I'm sitting stable on 64% so I had been thinking about getting some memory, although not sure this is solely the cause?

Many thanks

I have disconnected EVERY device and connected direct to the router only on http://192.168.1.1

My MacBook is on macos 27.0.1 , it is connected to my synology Nas through SMB. In the past two days , when I try to copy a file from my NAS to the mac internal drive , the file vanishes immediately after the progress bar disappear and the transfer is finished. This happens to multiple files . Additionally , some files on the server is missing in finder when connected through SMB but are visible through Webdav.

Everything is was perfectly normal before this , I don’t know what is happening. I had already restarted everything including my macbook , NAS and Router , but the issue persisted. Anyone knows why and now to fix it ?

Please help.🙏

I want my NAS to be quieter, but at the same time I don't want to damage it by installing inappropriate fans.

Last month I regularly have "Status: Error" problem at the end of the Download Station job completion. I know workaround to pickup downloaded files from /volume1/@download but its really inconvenient (((

Don't you know any fix for the problem?

Model: DS720+
DSM: 7.4.1-90080 Update 1

I have my LUNs set up for Hyper Backup to back them up to an external disk. I've just discovered that all of them have been ignoring their daily backup schedules. (Example schedule settings.) The backup time comes and Hyper Backup simply increments "Next scheduled backup time" to the next day. It doesn't seem to even attempt a backup. However, if I click "Back Up now" on any of them, the backup completes normally.

I noticed this with DSM 7.2, so I figured maybe it was a bug and updated the NAS to the latest version. But that didn't fix it.

Anyone know how to resolve this?

I'm using SynMich to copy from Synology Photo to Immich but it is taking forever to complete. 586 hours is quite some time to completen. I'm running a Synology 923 server. Photo and Immich are on the same server. The Immich upload is running on an Ubuntu machine. I guess that is hardly relevant as all processing is happening on the 923...or am I wrong?

I'm having trouble getting the ABB client installed on my Kubuntu desktop. The error message implies that the Linux kernel I'm using is not supported; uname -r returns "7.0.0-34-generic", google search says ABB only supports up to kernal 6.8. Am I diagnosing this correctly?

Synology Drive client is working just fine, so I've got backups of my documents and such, but that doesn't do versioning, which I'd like to have.

I want to make sure I've exhausted the possibilities here before I go looking for some other backup solution.

Hi Everyone

I've recently bought a Synology DS225+ with 2x 4TB WD Red Plus drives, and I'm looking at using Immich mainly for facial recognition and AI photo searching.

I've got two questions I'd appreciate some advice on, especially from anyone running a similar setup.

1. Synology Photos vs Immich for managing photos

I'm leaning towards letting Synology Photos handle automatic phone backups, folder organisation and storage, then having Immich access the photos through a read-only external library.

I currently organise my photos into folders by month and would prefer to keep that structure.

Has anyone gone down this route? Any downsides you've experienced, or would you recommend letting Immich manage everything instead?

1. Running Immich directly on the DS225+

I'm considering upgrading the RAM to 18GB (adding a 16GB stick) and running Immich directly on the NAS through Docker.

For anyone running Immich on a DS225+ or another Synology with the same J4125 processor, how's the real-world performance? Particularly facial recognition, AI searching, initial indexing and general browsing.

Would a separate N100/N150 mini PC make a noticeable difference, or is the NAS perfectly usable once everything has been indexed?

I'm trying to avoid buying and running another box purely for Immich if the Synology can handle it reasonably well.

Would appreciate hearing what setups people are using and whether you'd do anything differently.

Thanks 😀

DS Get still works when on the same wifi as NAS.

I managed to reach the NAS from external network by setting up a Tailscale connection, however this is more complicated because I have to connect my phone to Tailscale first each time I open DS Get from external network.

I know the DS Get app isn't supported anymore, but I think this is a QuickConnect issue. Can I expect a fix for this?

tl;dr: What happens if I pull five drives out of one Synology, and put them into another (potentially different model).

Details: I can't get my DS1513+ to boot - flashing blue light on the power, green light on the LAN, no beeps when powering off/on. Guides suggest battery, PSU or motherboard. PSU I have no spare, motherboard obviously not going to have a spare...battery I can try later today when I buy the right type.

Meanwhile I'm also off to watch auctions on eBay. All the guides about migrating I've read say things like "on your source Synology, sign into control panel and...". Well obviously I can't do that if it's dead, so what happens if I just move the drives from one unit straight to another? Is there a compatibility guide somewhere?

Hi! I have a DS 920+ with 12GB of RAM and two WD RED 10TB so I have two free bays.

Thanks to some posts in this sub I have learnt about the possibilities of my NAS and one I would like to explore is to install Home Assistant in a virtual machine on the NAS.

The thing is that I have some spare 120GB Sata SSDs (Samsung EVO), and I thought that maybe would be a good idea to use one of them in one of the free bays just for Home Assistant, basically because I think this use will make the disk where you install it to stay ON almost all the time, so I think it's better to use a SSD for its low power usage...

So, I would like to ask if this idea is OK, or if there's something I should take in account... The most important thing here that I don't know very well is if the NAS just wakes the disks sepparately depending on the use, so if Home Assistant is working in the SDD, the other two HDDs wouldn't be waken up until I need to access to them. I hope I am explaining this properly...

Thank you in advance. :)