Business CommunityControllersBUG?: custom DDNS config is ignoring https://
Controllers

BUG?: custom DDNS config is ignoring https://

BUG?: custom DDNS config is ignoring https://

BUG?: custom DDNS config is ignoring https://
BUG?: custom DDNS config is ignoring https://
a week ago
Tags: #DDNS
Model: Omada Software Controller (Windows)  
Hardware Version:
Firmware Version: 6.2.10.15

hi all,

 

I wanted to go away from my previous DDNS provider coding my own API, but it seems, there is apparently a bug.

Even if the URL contains https://

https

 

it is apparently ignored as I get always http response 301 - moved permanently - which occurs when I try to access the API via plain http://.....

301

 

any idea? did I something wrong or is this a bug?

 

 

/BR ZoloNN ----------------------------------------------------------------------- Omada 2x ER605(UN) v2.0 + SG2008P(UN) V3.20 + SG2218 V1.20 + 2x SG2008 V4.20 + 3x EAP615-Wall(EU) V1.0 CET (GMT+1)
0
0
#1
6 Reply
Re:BUG?: custom DDNS config is ignoring https://
a week ago

Hi @ZoloNN 

Thanks for reaching out to TP-Link Business Forums.

 

Thank you for bringing your topic to our forums.

May I know who is your DDNS provider?

What is the firmware and hardware version of your gateway?

Please always update your gateway to the latest version to ensure better performance.

Also, please make sure that you have entered the correct custom URL.

You can refer to this Custom DDNS Is Not Working - Business Community

Have a nice day!

 

 

0
0
#2
Re:BUG?: custom DDNS config is ignoring https://
a week ago

Hi @Gabriel-TP,

 

answers can be found in the thread header and in text, but to summarize (I've added the Gateway info too):

  • Controller type: Windows version
  • Software version: 6.2.10.15
  • Gateway type: ER605 v2.0
  • Gateway FW: 2.3.3
  • DDNS provider: my own API on my webserver written in PHP

 

bug symptoms:

even the URL contains "https://" (see picture above) I receive "301 - Moved Permanently", which occurs when accessing via plain unencrypted "http://"

(which sane person sends unencrypted username/password via public internet????)

 

proof:

http

 

/BR ZoloNN ----------------------------------------------------------------------- Omada 2x ER605(UN) v2.0 + SG2008P(UN) V3.20 + SG2218 V1.20 + 2x SG2008 V4.20 + 3x EAP615-Wall(EU) V1.0 CET (GMT+1)
0
0
#3
Re:BUG?: custom DDNS config is ignoring https://
Saturday

Hi @ZoloNN 

 

This seems to be related to the WAN configuration. Could you provide us with the WAN configuration settings here?

Thanks for your understanding.

0
0
#4
Re:BUG?: custom DDNS config is ignoring https://
Sunday

Hi @Gabriel-TP,

 

WAN on site 1 is using static IP address, on site 2 DHCP is used and both are working fine. no advanced settings are used.

 

 

 

/BR ZoloNN ----------------------------------------------------------------------- Omada 2x ER605(UN) v2.0 + SG2008P(UN) V3.20 + SG2218 V1.20 + 2x SG2008 V4.20 + 3x EAP615-Wall(EU) V1.0 CET (GMT+1)
0
0
#5
Re:BUG?: custom DDNS config is ignoring https://
20 hours ago

Hi @ZoloNN 

 

To better assist you, I've created a support ticket via your registered email address and the ticket ID is TKID260457348. Please check your email box and ensure the support email is well received. Thanks!

0
0
#6
Re:BUG?: custom DDNS config is ignoring https://
10 hours ago

Hi @Gabriel-TP,

 

while writing the anwer to the support case, I've found my own error in the URL - I have forgotten one "/" character in Update-URL:

 

https://api.**********.eu/ddns/?user=[USERNAME]&passwd=[PASSWORD]&host=[DOMAIN]

 

custom DDNS is now working as expected, case closed.

 

 

/BR ZoloNN ----------------------------------------------------------------------- Omada 2x ER605(UN) v2.0 + SG2008P(UN) V3.20 + SG2218 V1.20 + 2x SG2008 V4.20 + 3x EAP615-Wall(EU) V1.0 CET (GMT+1)
0
0
#7

Information

Helpful: 0

Views: 144

Replies: 6

Tags

DDNS
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.