Search found 93 matches
- 31 Oct 2020, 13:10
- Forum: Network & Remote Access
- Topic: Remote access with DuckDNS
- Replies: 9
- Views: 6156
Re: Remote access with DuckDNS
The "username" of DuckDNS actually refers to the token. The following is an example. e.g. username = 0e44j718-3b1a-494c-99gd-0f6329e6fa6d(token) password = badman479264 hostname = badman.duckdns.org Hi TMzethar. That worked! I have intechanged the information as described in my first post...
- 31 Oct 2020, 02:02
- Forum: Initialization
- Topic: F2-221 Great onboarding experience overall (diminished by non-existent guide for Linux & ChromeOS)
- Replies: 2
- Views: 1718
F2-221 Great onboarding experience overall (diminished by non-existent guide for Linux & ChromeOS)
As a newbie to things NAS, my onboarding experience has been great overall. Assembling the hardware was a breeze. Next, was initialising the device and setting up the operating system (TOS 4.3) which was gracefully handled by a very user-friendly Initialisation wizard. The single let down for me was...
- 30 Oct 2020, 16:27
- Forum: Network & Remote Access
- Topic: Remote access with DuckDNS
- Replies: 9
- Views: 6156
Remote access with DuckDNS
I use DuckDNS for remote access to my Home Assistant so it's the natural pick for my TNAS remote access. However, I could not get a "Connected" Connection Status when I click the "Apply" button in the Remote Access setup window. My guess is that this is because TNAS insists on us...