Unable to publish some service

Post your questions about myQNAPcloud service here.
Post Reply
matejkovacik
New here
Posts: 2
Joined: Thu May 02, 2019 3:22 am

Unable to publish some service

Post by matejkovacik » Thu Jan 09, 2020 10:29 pm

Hi guys, I am running QNAP TS128A with the latest firmware 4.4.1.1146 and having recently troubles with publishing services...

See here: Image

Configuration of router and NAS should be OK.

Image

UPnP on the router is enabled, some services are running, but for example VPN with L2TP services and some other I cannot get running. I have no clue why.

Image

Normally, I can access my NAS via the internet and public IP. All the ports should be opened (I have double checked with my internet provider) and there is no firewall enabled on my router.

Here is the diagnostics from the NAS:

Code: Select all

------ NAT PMP Diagnostics ------
initnatpmp() returned 0 (SUCCESS)
using gateway : 192.168.1.1
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned 0 (OK)
Public IP address : 176.114.255.6
epoch = 44724516
closenatpmp() returned 0 (SUCCESS)
------ UPnP Diagnostics ------
upnpc : miniupnpc library test client. (c) 2006-2011 Thomas Bernard
Go to http://miniupnp.free.fr/ or http://miniupnp.tuxfamily.org/
for more information.
List of UPNP devices found on the network :
 desc: http://192.168.1.1:1900/rootDesc.xml
 st: urn:schemas-upnp-org:device:InternetGatewayDevice:1

Found valid IGD : http://192.168.1.1:1900/ctl/IPConn
Local LAN ip address : 192.168.1.3
Connection Type : IP_Routed
Status : Connected, uptime=44724518s, LastConnectionError : ERROR_NONE
  Time started : Fri Aug 10 00:59:51 2018
MaxBitRateDown : 8388608 bps   MaxBitRateUp 4194304 bps
ExternalIPAddress = 176.114.255.6
 0 TCP  8080->192.168.1.3:8080  'cd310c110aa9d164fae506a932a37ae1-Web Admin' ''
 1 TCP  4433->192.168.1.3:4433  'uTorrentMac/1870(41339) at 192.168.1.3:4433' ''
 2 UDP  1194->192.168.1.3:1194  'cd310c110aa9d164fae506a932a37ae1-QVPN (OpenVPN Se' ''
 3 TCP 18768->192.168.1.3:18768 'NAT-PMP 18768 tcp' ''
 4 UDP 18768->192.168.1.3:18768 'NAT-PMP 18768 udp' ''
 5 TCP  6564->192.168.1.3:6564  'NAT-PMP 6564 tcp' ''
 6 TCP  8081->192.168.1.3:8081  'cd310c110aa9d164fae506a932a37ae1-Secure Web Serve' ''
 7 UDP  4500->192.168.1.3:4500  'cd310c110aa9d164fae506a932a37ae1-QVPN (L2TP/IPSec' ''
 8 UDP  1701->192.168.1.3:1701  'cd310c110aa9d164fae506a932a37ae1-QVPN (L2TP/IPSec' ''
GetGenericPortMappingEntry() returned 713 (SpecifiedArrayIndexInvalid)
Any ideas?

Thx!

Matej

dolbyman
Guru
Posts: 19727
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: Unable to publish some service

Post by dolbyman » Thu Jan 09, 2020 10:33 pm

dont use upnp (disable ot on the router)
never expose your nas plain to the web

if possible use a vpn server on your router

matejkovacik
New here
Posts: 2
Joined: Thu May 02, 2019 3:22 am

Re: Unable to publish some service

Post by matejkovacik » Fri Jan 10, 2020 3:30 am

Hi Dolbyman,

thanks for reply. Is there any way how I can I figure out why I am getting for some services status "Error" and for some not? Logging? This is not only about VPN. It used to work before. I did some test and so far I found something interesting - if I try to enable any port with one, two or three digits - it does not work. If I try to enable port with four digits - working. There is no limitation on ISP side (checked) and also no limitation on router - Tplink Archer C2300. Could it be related to latest firmware issue?

Matej

dolbyman
Guru
Posts: 19727
Joined: Sat Feb 12, 2011 2:11 am
Location: Vancouver BC , Canada

Re: Unable to publish some service

Post by dolbyman » Fri Jan 10, 2020 3:52 am

maybe a router firmware update that prevents port forwards of stuff like AFP (bad idea)

So use my advice and remove all of this for the sake of VPN ... otherwise prepare to get hacked (and potentially lose all your data)

andreamb
First post
Posts: 1
Joined: Wed Oct 19, 2016 3:02 am

Re: Unable to publish some service

Post by andreamb » Sat Aug 29, 2020 5:52 pm

Hi, I also had this trouble since yesterday. my vpn access went down. The situation seem very similar and I had this issue on the Secure Virtualization port since a while too (8089).

The diagnostic return a "SpecifiedArrayIndexInvalid" on port 1701 .

Did you solve it ? Any other suggestions ??

workarounding not using UPNP is not the solution, solution is find the way services may work correctly..

It seems more an issue of the service QVPN itself ...

Thanks in advance Andrea

Post Reply

Return to “myQNAPcloud service”