Page 1 of 1

[INFO] Twonky Server 7.2.8 Web Interface Remote Access

Posted: Thu Aug 07, 2014 4:35 pm
by phibertron
While working on 7.2.8 for something else, I stumbled upon this,
It looks like it possible to enable working remote access using twonky settings again
Im not sure when this started working again, probably in one of the 7.2.x versions

My solution prior to this is located here:
How to enable remote access for Twonky Server 7.2.x
http://twonkyforum.com/viewtopic.php?f=2&t=11402

note: Twonky 7.2.x Special Search Version 6 is my latest version
.

Re: [INFO] Twonky Server 7.2.8 Web Interface Remote Access

Posted: Thu Aug 07, 2014 4:38 pm
by phibertron
There are various topics on this forum about enabling remote access
Here is a summary of the settings involved to enable it
that are located in the twonkyserver.ini
# access to web config pages, 0 for denied, 1 for local only, 2 for open
enableweb=

# enable https remote connections
enabletls=

# http server port for remote access
httpremoteport=

# dynamic dns prefix for remote access, including http:// or https://
dyndns=

# enable remote access
remoteaccess=

# for protection of the web config pages
accessuser=

# for protection of the web config pages
accesspwd=

Re: [INFO] Twonky Server 7.2.8 Web Interface Remote Access

Posted: Thu Aug 07, 2014 4:41 pm
by phibertron
# access to web config pages, 0 for denied, 1 for local only, 2 for open
enableweb=2
There should be no need to change this setting, by Default this setting = 2
note: If set to anything other than 2, remote access will not work

If one had to change it, either edit the twonkyserver.ini or use an rpc call to set it, server restart is required

Code: Select all

http://x.x.x.x:9000/rpc/set_option?enableweb=2

Re: [INFO] Twonky Server 7.2.8 Web Interface Remote Access

Posted: Thu Aug 07, 2014 4:45 pm
by phibertron
# enable https remote connections
enabletls=1
By Default this setting = 1
Which means that it will only HTTPS connections will work
If you intend to use HTTP for remote access, it must = 0

NOTE: it appears the HTTPS isn't working as expected, so we are forced to use HTTP

If one had to change it, either edit the twonkyserver.ini or use an rpc call to set it, server restart is required

Code: Select all

http://x.x.x.x:9000/rpc/set_option?enabletls=0
.

Re: [INFO] Twonky Server 7.2.8 Web Interface Remote Access

Posted: Thu Aug 07, 2014 4:49 pm
by phibertron
# http or https server port for remote access
httpremoteport=
By default this setting has no value, also by default the internal port for Twonky is 9000
so one cant use that for the remote access port

If one had to change it, either edit the twonkyserver.ini or use an rpc call to set it, server restart is required

Code: Select all

http://x.x.x.x:9000/rpc/set_option?httpremoteport=9090
.

Re: [INFO] Twonky Server 7.2.8 Web Interface Remote Access

Posted: Thu Aug 07, 2014 4:52 pm
by phibertron
# dynamic dns prefix for remote access, including http:// or https://
dyndns=
By default this setting has no value
the value uses here is what is used in the links generated by twonky for remote access

NOTE: if enabletls=1, you must use https, if not use http
NOTE: since enabletls=1 isn't working correctly, enabletls=0 is needed

For example:
If you
If one had to change it, either edit the twonkyserver.ini or use an rpc call to set it, server restart is required

Code: Select all

http://x.x.x.x:9000/rpc/set_option?dyndns=http://myserver.dyndns.com
.

Re: [INFO] Twonky Server 7.2.8 Web Interface Remote Access

Posted: Thu Aug 07, 2014 4:55 pm
by phibertron
# enable remote access
remoteaccess=
By default this setting has no value, meaning its not enabled
This must be set to = 1 for remote access to work

If one had to change it, either edit the twonkyserver.ini or use an rpc call to set it, server restart is required

Code: Select all

http://x.x.x.x:9000/rpc/set_option?remoteaccess=1
.

Re: [INFO] Twonky Server 7.2.8 Web Interface Remote Access

Posted: Thu Aug 07, 2014 4:59 pm
by phibertron
# for protection of the web config pages
accessuser=
It is HIGHLY RECCOMENDED TO USE ONE when enabling remote access
If one had to change it one can use the web interface, or edit the twonkyserver.ini or use an rpc call to set it

Code: Select all

http://x.x.x.x:9000/rpc/set_option?accessuser=someusername
.

Re: [INFO] Twonky Server 7.2.8 Web Interface Remote Access

Posted: Thu Aug 07, 2014 5:12 pm
by phibertron
# for protection of the web config pages
accesspwd=
It is HIGHLY RECCOMENDED TO USE ONE when enabling remote access
If one had to change it one can use the web interface, or edit the twonkyserver.ini or use an rpc call to set it

NOTE: this will ALSO affect the internal web interface access, sadly there is no way to separate the two

Code: Select all

http://x.x.x.x:9000/rpc/set_option?accesspwd=somepassword
.

Re: [INFO] Twonky Server 7.2.8 Web Interface Remote Access

Posted: Thu Aug 07, 2014 5:21 pm
by phibertron
NOTE: At present HTTPS is NOT working correctly, so we are forced to use HTTP, using this method

The following example is for HTTP remote access
# access to web config pages, 0 for denied, 1 for local only, 2 for open
enableweb=2

# enable https remote connections
enabletls=0

# http server port for remote access
httpremoteport=9090

# dynamic dns prefix for remote access, including http:// or https://
dyndns=http://myserver.dyndns.com

# enable remote access
remoteaccess=1

# for protection of the web config pages
accessuser=myusername

# for protection of the web config pages
accesspwd=mypassword

Code: Select all

http://myserver.dyndns.com:9090

Re: [INFO] Twonky Server 7.2.8 Web Interface Remote Access

Posted: Thu Aug 07, 2014 7:12 pm
by phibertron
When it comes to time to put a port forward on your router
Do NOT port forward to 9000, that wont work as expected to
You SHOULD, use a port forward to whatever you set httpremoteport =
In the above example, it would be 9090
As for what external port on the router you choose to forward to 9090, that's up to you

Re: [INFO] Twonky Server 7.2.8 Web Interface Remote Access

Posted: Fri Aug 08, 2014 1:16 am
by phibertron
In regards to HTTPS not working
I was able to get it working, once I resolved a different issue

[BUG] Twonky Server Port number issue with 7.2.x and 7.3.x
http://twonkyforum.com/viewtopic.php?f=2&t=11710