alx0101

I see that code if I attempt to activate an app that is not installed.

https://alxr0101.github.io/ (DSM 6/7) I have updated the above page to generate required login session and URL to activate the app/s :- 1. LOGIN link (supports 2FA codes as well..just leave blank if no 2FA used) 2. ACTIVATION for each ActiveBackup app: Business, Google Workspace(GSuite) or Office365 a) First install the app/s required to activate (does not appear to pre-activate.."success:false") b) open a new INCOGNITO mode tab to ensure clean "session" from current logged in tab c) generate the LOGIN link and paste that to the tab (check plenty of 2FA code time left..only need 2FA time for this step) (at the end of the result line, should see "{"success":true}" d) copy each/all of the required activation codes for the required app/s and paste into same tab (should see "success:true" message) Ensure to use an incognito tab. TESTED on DSM 7.1.1-42962 Update 6 for a 2FA and a non-2FA account TESTED on DSM 6.2.3-25426 Update 3 NOT TESTED with complex passwords but have URL-encoded the user/password.

Made no difference. The page basis set on URL's that also don't use URL encoding. I still found issues with the first authentication step and temporarily resolved by: a) disable 2FA b) set a simple password (no symbols..just letters and numbers) c) ensure to use a user that has admin rights. If you dont see a response "success: true" at first step then review above and retry.

Changing serial to start with those first alphanumerics worked, nothing else worked. What's the basis for this serial number ?

Makes sense. Will adjust. Meanwhile use simple user/passwords (set up a temp user admin account) just for activation.

Suggest temporarily set another admin account (with no 2FA) and use that after confirming it works for login to DSM GUI. It seems that DSM was still expecting 2FA for the username you set for the activation process. API error code states " 403 2-factor authentication code required"

Try putting %20cookie (instead of the (space)cookie. %20 is equiv to the space that seems to be required after the = sign. Also ensure your are using port 5001 (default) for https (what is your usual login port showing? If no port shows then it's been set to 443 and can leave blank as https:// sets it) Also ensure you paste these URL's into a NEW web browser incognito tab. The first URL generates a new SESSION, the second URL can then activate the service. Must paste into the same address bar as the first. See my URL generator DSM7 (for the first URL, I moved the &format=%20cookie param within the line but the order does not matter). https://alxr0101.github.io/ If you DO NOT SEE something like the below, then no point doing the second activation link. First link must return something like this:- SUCCESSFUL URL 1 login link must look like this.., ending in success..true) {"data":{"did":"1HKGYIY___lots of letters...._ JbtmS-xmg","sid":"8bZt__ lots of letters_____NHmDgFxHlOks"},"success":true} SUCCESSFUL second URL result is this:- {"data":{"activated":true},"success":true} Ensure also the username is an admin and the password is nothing complicated ( re: characters and symbols) in case your browser is messing up the encoding.

Assuming your username and password is correct, you did not paste into a new incognito tab (to start a new session).

I've created a page that generates the links required. https://alxr0101.github.io/ Just input your details, hit the Get Links button and then copy each of the two links generated. IMPORTANT: Need to run these in a "clean" tab...ie cannot be logged in. Easiest is run a new INCOGNITO WINDOW (chrome) or equivalent in EDGE ("new InPrivate WIndow")/Firefox etc. Then paste each into the SAME address bar, the LOGIN one first followed by the ACTIVATE.

Prob because you switched from the browser already logged in. Just open an incognito tab in existing browser.

Firstly, prep the two URL lines fully, for copy and paste into the address bar. (i used CHrome on a brand new installation of DSM 7.1.1-42962 Update 1 ) important: START AN INCOGNITO tab to ensure independence from any existing logged in sessions !!!! PAste the FIRST LINE in: If using port 5000 and it is http (not https)....whatever your NAS is set to..eg port 5001 for https replace IP_ADDRESS, USERNAME and PASS below with your admin details:- FIRST URL http://IP_ADDRESS:5000/webapi/auth.cgi?api=SYNO.API.Auth&version=3&method=login&account=USERNAME&passwd=PASS&format=%20cookie FIRST URL LINE result looks like:- (replace some of string with some etc_etc_etc) {"data":{"did":"gL9TOKetc etc etc.........pLh9mJt6w","sid":"bihju7DywBW8etc_etc_etcxHZXQ"},"success":true} If you do not get something like above, recheck your FIRST LINE URL...no point proceeding to the next step until you see something similar to above, with long strings for "did" and "sid". then paste in the same address bar the second link: replace SERIALNUMBER with the SERIAL NUMBER from your DSM control panel INFO page: SECOND URL http://IP_ADDRESS:5000/webapi/entry.cgi?api=SYNO.ActiveBackup.Activation&method=set&version=1&activated=true&serial_number="SERIALNUMBER" SECOND URL LINE result: {"data":{"activated":true},"success":true}

I've successfully loaded DMS6 and DSM7 on a few laptops and have never had to modify for lid closure. They reboot fine also with lid closed:- Acer Aspire 1810T synoboot 103b DS3615xs DSM 6.2.3-25426 Update 3 Acer 7950G synoboot 103b DS3615xs DSM 6 Acer Aspire 5560 synoboot 103b DS3615xs DSM6 Toshiba R830 tinycore-redpill.v0.9.3.0 DS3622xs+ DSM 7.1.1-42962 Update 3 All above are quite ancient (10+ years old and saved from the scrapheap) (although I'm only keeping the ones with USB3.0 ports). The 7950G has dual drives but is fan noisy (despite CPU thermals sorted). The 1810T has been in flawless service for several months now.

I finally got around to updating it. Now on jun 103b DSM 6.2.3-25423, DS3615+ ; The monitoring issue eventually self-corrected (go figure) but certainly some gremlins in DSM 5 such as having to manually start file services after a restart. DSM 5 provided sterling service though..over 1100 days without a reboot or hiccup. Onwards with DSM6. *** ACER 7950G laptop (std);2x HDD: jun103b DSM 6.2.3-25423, DS3615+ ; ACER 1810T laptop (std); jun103b DSM 6.2.3-25423, DS3615+ ; HP N54L; jun103b DSM 6.2.3-25423, DS3615+; HP Gen8; jun103b DSM 6.2.3-25423, DS3615+ ; HP Slimline SFF s3760a plus PCIe NIC Intel CT; jun103b DSM 6.2.3-25423, DS3615+ ;

Additional info re RESOURCE MONITOR. I just discovered that Resource Monitor works fine from an android phone (on the Samsung browser MOBILE mode). And if I switch the mobile browser to DESKTOP then that reproduces the "Network" issue. I tried latest FIREFOX and CHROME on desktop and still get the above error, unless I use developer mode and switch to a mobile config. Seems a browser compatibility issue and not a service issue so will search alternate thread and repost. Summary: Resource monitor only works via browser set to MOBILE mode (such as for iPad). DESKTOP mode returns "network" issue.

Related issue, the RESOURCE MONITOR also no longer works. It displays with a "CONNECTION FAILED. PLEASE CHECK YOUR NETWORK SETTINGS" in a popup OK box. It does not display info in the Widget either. Again...where should I start tracking down why it fails?

DSM 5.2-5565 Update 2 Server has operated fine for couple of years. But I notice that I have to toggle off/on the FILE SERVICES (Windows SMB, WebDAV are the ones I need) off and back on again after EVERY BOOT UP. Only then do Windows and WebDAV shares function. I otherwise have full access to the server (ie. webGUI, SSH) and the server is active on the LAN. I have full root SSH terminal and WinSCP access. Is there a methodical process to follow so I can review LOGS etc and determine WHY and rectify the non-start of these services? Am sure it used to work but stumped as to where to start resolving this.

Did a clean install today. Seems to load fine but not tested extensively. stock HP N54L / 8GB. Now the bad news- I did the above in exasperation at the very unclean upgrade from 5.0- 4493-7 --> 5.1 --> 5.2 All seemed to upgrade fine (using relevant version Xenoboot at each step) but then things went pear shaped:- upon reboot after "successful" 5.2 upgrade, I could not get into NAS. Reason:- eth0 had not set an IP address! Manually set IP and netmask(which didnt stick between reboots) and things like Time Line now dont work. By this stage I did a "clean" install (to a spare new drive) and confirmed no prob with eth0 for that. Really regret upgrading and could not downgrade from 5.2 to 5.1 as it threw an error can't revert from 5565. Any suggestions?