- 716
- 389
- NAS
- RS1221+, RS819, RS217
- Operating system
- macOS
- Mobile operating system
- iOS
Having a problem connecting CMS to a single NAS via HTTPS.
If I let CMS auto-configure the connection it leaves me with plain HTTP on port 5000:
If I set HTTPS manually on port 5001, either at initial setup or via an edit of the existing CMS connection:
It instantly returns the following caption:
I have no such issue on my other NASes but the NAS with the issue (Dragon - an RS217) is the only unit I have running the DSM 7 beta (7.0-41222) with all the others running DSM 6.2.4-25556.
I have no issues connecting to the DSM web service on the troubled NAS via HTTPS on port 5001; I've not spotted any difference in configuration for this NAS either, apart from the differences introduced in DSM 7. I've never had the RS217 under the CMS umbrella before so no idea if it worked on DSM 6. Outside of the HTTPS issue the CMS link works flawlessly and even offers the new DSM 7 icons when you click on the CMS Application tab.
Anyone run into this before or can point me at something to check or change?
If I let CMS auto-configure the connection it leaves me with plain HTTP on port 5000:
If I set HTTPS manually on port 5001, either at initial setup or via an edit of the existing CMS connection:
It instantly returns the following caption:
I have no such issue on my other NASes but the NAS with the issue (Dragon - an RS217) is the only unit I have running the DSM 7 beta (7.0-41222) with all the others running DSM 6.2.4-25556.
I have no issues connecting to the DSM web service on the troubled NAS via HTTPS on port 5001; I've not spotted any difference in configuration for this NAS either, apart from the differences introduced in DSM 7. I've never had the RS217 under the CMS umbrella before so no idea if it worked on DSM 6. Outside of the HTTPS issue the CMS link works flawlessly and even offers the new DSM 7 icons when you click on the CMS Application tab.
Anyone run into this before or can point me at something to check or change?