Since Dyndns is stopping 7/may/2014, I tried to use me.mycloudnas.com as my ddns.
This works fine for most things except when I try logging into transmission via transdroid, it fails
Using dyndns works fine
the address in transdroid is; myusername@me.mycloudnas.com
Mycloudnas doesn't seem able to handle a user name.
Does anyone know if it is possible to use mycloudnas for ddns or do I need to get an noip account?
Thanks
Maurice
transmission using user@me.mycloudnas.com
-
- Getting the hang of things
- Posts: 56
- Joined: Tue Oct 13, 2009 8:34 pm
- Location: Ireland
- schumaku
- Guru
- Posts: 43579
- Joined: Mon Jan 21, 2008 4:41 pm
- Location: Kloten (Zurich), Switzerland -- Skype: schumaku
- Contact:
Re: transmission using user@me.mycloudnas.com
What for does Transdroid require a username? Not for the DDNS part at least...
Completely unrelated to establish the connection - all you need is an IP address at the end of the day, represented by a DNS A record with an IPv4 address, pointing to the WAN IP address in front of your NAT router.
Nothing from here is elated to any DDNS service:
Might happen the client does combine the username configured to login to Transmission is combined into a single configuration field.
Can you reach the Transmission Web UI from a browser like http://me.myqnapcloud.com:9091/ and can authenticate using username and password? If yes, configure the same username, myqnapcloud.com name, port, username and password.
Completely unrelated to establish the connection - all you need is an IP address at the end of the day, represented by a DNS A record with an IPv4 address, pointing to the WAN IP address in front of your NAT router.
Nothing from here is elated to any DDNS service:
Might happen the client does combine the username configured to login to Transmission is combined into a single configuration field.
Can you reach the Transmission Web UI from a browser like http://me.myqnapcloud.com:9091/ and can authenticate using username and password? If yes, configure the same username, myqnapcloud.com name, port, username and password.
-
- Getting the hang of things
- Posts: 56
- Joined: Tue Oct 13, 2009 8:34 pm
- Location: Ireland
Re: transmission using user@me.mycloudnas.com
Thanks schumaku for your reply.
From a webbrowser http://me@me.myqnapcloud.com:9091/ works fine, but asks for user name and pass
Transdroid the android app for transmission, sends the request as;
http://me@me.myqnapcloud.com:9091 which fails yet
http://me@me.dnydns.com:9091 works fine.
which leads me to conclude that mycloudnas won't resolve a username.
Mycloudnas will work for other peripherals.
I suspect that my option is just to move to noip.com
From a webbrowser http://me@me.myqnapcloud.com:9091/ works fine, but asks for user name and pass
Transdroid the android app for transmission, sends the request as;
http://me@me.myqnapcloud.com:9091 which fails yet
http://me@me.dnydns.com:9091 works fine.
which leads me to conclude that mycloudnas won't resolve a username.
Mycloudnas will work for other peripherals.
I suspect that my option is just to move to noip.com
- schumaku
- Guru
- Posts: 43579
- Joined: Mon Jan 21, 2008 4:41 pm
- Location: Kloten (Zurich), Switzerland -- Skype: schumaku
- Contact:
Re: transmission using user@me.mycloudnas.com
...same form the mobile phone Web browser?maurice1 wrote:From a webbrowser http://me@me.myqnapcloud.com:9091/ works fine, but asks for user name and pass
Both should behave the same - unless me.myqnapcloud.com can't be resolved on the android device, or the App does something strange. What else the App does around - with protocol (http://), username (me@), or the port(:9091) - the DDNS system will never see it.maurice1 wrote:http://me@me.myqnapcloud.com:9091 which fails yet
http://me@me.dnydns.com:9091 works fine.