Re: Issues connecting to my godaddy hosted website...

Poolelad · ‎04-12-2017

I've read this thread with interest, and I hope yiur move to a new web hosting service sorts your problem. I don't think it will, reason, I've had the same problem for a year now with GoDaddy and I'm running a hH6, which blocks the Godaddy traffic after 2-3 days of use. Reason I believe it's hub related and not goDaddy.

When it first happened I spend 90mins on the phone with Godaddy support out of the USA, and they could not see what I was experiencing. I've since found that in one way they were correct as looking throught the Godaddy hosted client it looks normal. Today having power cycled the HH6 on Friday it went again, and I can tell as it blocks FTP traffic (not only to Godaddy) but inbound from other sites.. So FTP uploads freeze, and the ftp log shows timeout host unreachable, and ftp session fails.

Bear in mid I have no port forwarding on this as I have never ever needed it.

So today whilst my hosted site looked down to everything behind my HH6, I logged in from an enirely different domain, and sure enought my website looked good, I could access cpanel and manage my host no problem. I cant do that when the HH6 locks up and blocks ftp sessions. Even access to my Godaddy webhome cpanel is not accessible it times out.

Never ever had this grief on a HH5 it just ran fine.

So, without doing anything else, I power cycle the HH6, and the ftp block disappears, I can access cpanel on my webhome, and off it goes again for a day or so.

Like I say, moving host might solve your problem, but I'm not convinced it's a Godaddy issue, when something so simple as a power cycle of the HH6 cures the problem. Sad thing is, the HH6 will eventually fail through regular power cycling.

It's a pain, and after a year of the same issue I don't think anybody (apart from me knows how to fix it quickly).

Regards

Pl

tvol · ‎04-12-2017

Hi Poolelad

The issue we were facing back in October was definitely related to GoDaddy and their internet peering with Tata for BT-broadband bound traffic - and was resolved without needing any HH restarts. It sounds like you may have a different issue - perhaps worth starting a new thread to see if anyone else on here has seen similar or can help you further?

Cheers

tvol.

licquorice · ‎04-12-2017

@Poolelad I have moved your post to start a new thread as this does appear to be a different problem and the other thread was marked as solved.

XRaySpeX · ‎04-12-2017

Please post your full Router Stats. For a Home Hub see on here: Broadband Top Tips . Full router stats are key to any speed & connection issues.

___________________________________________________________________________
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on left hand side

Poolelad · ‎05-12-2017

Folks

Firstly thanks for your guidance in adding an item to the forum.

As I replaced the router last Friday the logs begin from there, here's the other info requested.

DSL uptime:

1 Days, 2 Hours 42 Minutes 23 Seconds

Noise margin:

8.4 dB / 7.8 dB

Line attenuation:

21 dB

It's failed to upload an ftp session around 14:50 on 4th Dec, so that is captured below:

ppp1:TR69 ConnectionRequest Failed

16:32:09, 04 Dec.

ppp1:TR69 ConnectionRequest: processing request from ACS

16:29:15, 04 Dec.

BR_LAN:The DHCP options that are offered by the device (id:5): DiscoverOptions: 53,61,50,12,60,55 | DiscoverOption55: 1,3,6,15,31,33,43,44,46,47,121,249,252 | RequestOptions: 53,61,50,54,12,81,60,55 | RequestOption55: 1,3,6,15,31,33,43,44,46,47,121,249,252 | HostName: Flippy | VendorId: MSFT 5.0

16:29:15, 04 Dec.

DHCP Confirmation of Request

16:29:02, 04 Dec.

wl1:A WiFi device <AC:B5:7D:7C:EC:19> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

16:03:30, 04 Dec.

wl1.1:Device <84:8E:DF:A6:1A:32> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_REDSIDE_O1_2G])

16:03:06, 04 Dec.

wl1.1:A WiFi device <84:8E:DF:A6:1A:32> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_REDSIDE_O1_2G])

16:03:06, 04 Dec.

wl1.1:Device <84:8E:DF:A6:1A:32> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_REDSIDE_O1_2G])

16:02:45, 04 Dec.

wl1.1:A WiFi device <84:8E:DF:A6:1A:32> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_REDSIDE_O1_2G])

15:47:17, 04 Dec.

wl0.1:Device <F4:09:D8:CE:34:3D> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_REDSIDE_O1_5G])

15:45:39, 04 Dec.

DHCP Confirmation of Request

15:45:36, 04 Dec.

wl0.1:A WiFi device <F4:09:D8:CE:34:3D> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_REDSIDE_O1_5G])

15:06:31, 04 Dec.

15:06:30, 04 Dec.

DHCP Confirmation of Request

15:06:24, 04 Dec.

wl1:A WiFi device <04:52:F3:32:E0:0D> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

14:55:17, 04 Dec.

wl1:Device <FC:C2:DE:8A:28:D9> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

14:55:12, 04 Dec.

ppp1:TR69 connectivity to (pbthdm.bt.mo) has been closed

14:55:10, 04 Dec.

ppp1:TR69 connectivity to (pbthdm.bt.mo) has been initiated

14:55:10, 04 Dec.

InformResponse:TR69 receiving (HX�ٸͭ�e�-��j�B message

14:55:09, 04 Dec.

ppp1:TR69 event found : 4 VALUE CHANGE

14:55:09, 04 Dec.

ppp1:TR69 event found : 1 BOOT

14:55:08, 04 Dec.

ppp1:TR69 sending Inform message

14:55:07, 04 Dec.

ppp1:TR69 event found : 4 VALUE CHANGE

14:55:07, 04 Dec.

ppp1:TR69 event found : 1 BOOT

14:55:06, 04 Dec.

ppp1:TR69 sending Inform message

14:55:03, 04 Dec.

ppp1:TR69 creating new session with ACS

14:53:54, 04 Dec.

BR_LAN:The LAN DHCPv6 Server is active

14:53:54, 04 Dec.

BR_LAN:LAN Router Advertisement Setting Updated : M_flag = 0, O_flag = 1

Thanks

Poolelad · ‎05-12-2017

And the second part of the log is below:

14:53:54, 04 Dec.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

14:53:54, 04 Dec.

BR_LAN: Allocated address = 2a00:23c4:2254:1e00:8aa6:c6ff:fe3b:c0c5 (valid time = 2026291200 / preferred time = 2026291200)

ppp1: Allocated prefix = 2a00:23c4:2254:1e01::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:53:54, 04 Dec.

BR_LAN:The LAN DHCPv6 Server is inactive

BR_LAN:The DHCP options that are offered by the device (id:15): DiscoverOptions: 53,61,12,60,55 | DiscoverOption55: 1,3,6,12,15,28,40,41,42 | RequestOptions: 53,61,12,60,50,54,55 | RequestOption55: 1,3,6,12,15,28,40,41,42 | HostName: hmindoor | VendorId: udhcp 0.9.9-pre

14:53:54, 04 Dec.

BR_LAN:The LAN DHCPv6 Server is active

14:53:54, 04 Dec

14:53:54, 04 Dec.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/

DHCP Confirmation of Request

64 (valid time = 4293967296 / preferred time = 4293967296)

14:53:54, 04 Dec.

BR_LAN: Allocated prefix = 2a00:23c4:2254:1e00::/64 (valid time = 2026291200 / preferred time = 2026291200

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

14:53:53, 04 Dec.

BR_LAN:The LAN DHCPv6 Server is inactive

14:53:37, 04 Dec.

BR_LAN:The LAN DHCPv6 Server is active

14:53:37, 04 Dec.

:The LAN DHCP Server is active

14:53:36, 04 Dec.

BR_LAN:The LAN DHCPv6 Server is inactive

14:53:36, 04 Dec.

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

14:53:36, 04 Dec.

BR_LAN: Allocated prefix = 2a00:23c4:2254:1e00::/64 (valid time = 2026291200 / preferred time = 2026291200)

14:53:36, 04 Dec.

wl1:A WiFi device <44:33:4C:C7:9A:E2> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

BR_LAN: Allocated prefix = fdaa:bbcc:ddee::/64 (valid time = 4293967296 / preferred time = 4293967296)

14:53:36, 04 Dec.

BR_LAN: Revoked prefix = 2a00:23c4:2254:1e00::/64 (valid time = 2026291200 / preferred time = 2026291200)

ppp1:WAN DHCPv6 Mode : Statefull

14:53:35, 04 Dec.

wl1:Device <B4:82:FE:BC:18:82> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

14:53:35, 04 Dec.

BR_LAN:The DHCP options that are offered by the device (id:7): DiscoverOptions: 53,61,57,60,12,55 | DiscoverOption55: 1,33,3,6,15,28,51,58,59 | RequestOptions: 53,61,50,54,57,60,12,55 | RequestOption55: 1,33,3,6,15,28,51,58,59 | HostName: android-916e5f089922ab92 | VendorId: dhcpcd-5.5.6

14:53:35, 04 Dec.

14:53:29, 04 Dec.

wl1:(1/6) Channel Hopping initiated/Manually initiated

14:53:26, 04 Dec.

:The LAN DHCP Server is inactive

14:53:26, 04 Dec.

DHCP Confirmation of Request

14:53:20, 04 Dec.

wl1:A WiFi device <FC:C2:DE:8A:28:D9> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

14:53:20, 04 Dec.

wl0:A WiFi device <BC:30:7D:C3:05:8A> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV5G])

14:53:20, 04 Dec.

BR_LAN:The DHCP options that are offered by the device (id:15): DiscoverOptions: 53,61,12,60,55 | DiscoverOption55: 1,3,6,12,15,28,40,41,42 | RequestOptions: 53,61,12,60,50,54,55 | RequestOption55: 1,3,6,12,15,28,40,41,42 | HostName: hmindoor | VendorId: udhcp 0.9.9-pre

14:53:20, 04 Dec.

BR_LAN:The DHCP options that are offere 1,15,3,6,44,46,47,31,33,121,249,43 | HostName: nettie | VendorId: MSFT 5.0

14:52:50, 04 Dec.d by the device (id:13): DiscoverOptions: | DiscoverOption55: | RequestOptions: 53,61,50,12,81,60,55 | RequestOption55:

14:52:35, 04 Dec.

BR_LAN:The DHCP options that are offered by the device (id:16)ame: DiscoverOptions: | DiscoverOption55: | RequestOptions: 53,55,57,61

ption55: 1,121,3,6,15,119,252 | HostN: ns-iPad | VendorId:

14:51:45, 04 Dec.

ppp1: Allocated prefix = 2a00:23c4:2254:1e00::/56 (valid time = 2026291200 / preferred time = 2026291200)

14:51:45, 04 Dec.

Sorry for the smilies, I sent it as rich text clearly it has decided to determine some of the characters are html, apologies.

I had to split the log so you could see the whole sequence from the time it failed, but nit's over 20K characters in length, so the reason for the split.

Thanks

XRaySpeX · ‎05-12-2017

Please may we have your full Router Stats?

___________________________________________________________________________
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on left hand side

Poolelad · ‎06-12-2017

Apologies, here's the stats from the router:

This is a list of your BT Smart Hub settings and current statistics.

Product name:
BT Hub 6A
Serial number:
+084316+NQ63767757
Firmware version:
SG4B1000B316
Firmware updated:
02-Sep-2017
Board version:
1.0
Gui version:
1.64.0
DSL uptime:
0 Days, 8 Hours 53 Minutes 59 Seconds
Data rate:
5.00 Mbps / 39.97 Mbps
Maximum data rate:
8391 / 44732
Noise margin:
8.1 dB / 7.8 dB
Line attenuation:
21 dB
Signal attenuation:
VPI / VCI:
0/38
Modulation:
G_993_2_ANNEX_B
Latency type:
Fast Path
Data sent / received:
159 MB Uploaded / 434 MB Downloaded
Broadband username:
bthomehub@btbroadband.com
BT Wi-fi:
Active
2.4 GHz wireless network name:
BTHub6-WQXF
2.4 GHz wireless channel:
Smart (Channel 1)
5 GHz wireless network name:
BTHub6-WQXF
5 GHz wireless channel:
Smart (Channel 36)
Wireless security:
WPA2 (Recommended)
Wireless mode:
Mode 1
Firewall:
On
MAC address:
88:A6:C6:35:08:E3
Software variant:
-
Boot loader:
7.33.1

Regards

Pl

Poolelad · ‎11-12-2017

And again tonight regular rHub prevented all traffic with unable to locate DNS server, wherever I went.

Had to restart the router after this was reported:

18:27:07, 11 Dec.

wl0:IGMP join received for group 239.255.255.246 on interface wl0

18:27:07, 11 Dec.

wl0:IGMP group 239.255.255.246 on interface wl0 started by 192.168.1.65

18:27:07, 11 Dec.

wl0:IGMP group 239.255.255.246 on interface wl0 by 192.168.1.65 requested

18:27:04, 11 Dec.

wl1:A WiFi device <B4:82:FE:BC:18:82> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

18:27:04, 11 Dec.

wl1:Device <B4:82:FE:BC:18:82> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

18:27:04, 11 Dec.

wl0:A WiFi device <C4:73:1E:D4:42:DF> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV5G])

18:27:01, 11 Dec.

:The LAN DHCP Server is inactive

18:27:01, 11 Dec.

Regular as clockwork after 3 -4 days the whole thing locks up and needs a restart to bring it back to life.

Regards

Pl

Poolelad · ‎13-12-2017

And it's gone again same old story, same messages in the log, so now it's failing every 2 days.

log

This shows all events that have taken place on your BT Smart Hub since the last time it was

Page 1 of 172

ct

ppp1:TR69 creating new session with ACS

17:54:59, 13 Dec.

wl0:IGMP group 239.255.255.246 on interface wl0 ended by 192.168.1.65

17:54:59, 13 Dec.

wl1:Device <C4:73:1E:D4:42:DF> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

17:54:51, 13 Dec.

17:54:51, 13 Dec.

:DHCP Confirmation of Request

17:54:46, 13 Dec.

ppp1:The WAN DHCPv6 Client Process has successfully been launched on Vlan 36

00:06:23, 01 Jan.

:The LAN DHCP Server is active

00:06:23, 01 Jan.

wl0:IGMP join received for group 239.255.255.246 on interface wl0

00:06:22, 01 Jan.

wl0:IGMP group 239.255.255.246 on interface wl0 started by 192.168.1.65

00:06:22, 01 Jan.

wl0:IGMP group 239.255.255.246 on interface wl0 by 192.168.1.65 requested

00:06:13, 01 Jan.

00:06:13, 01 Jan.

00:06:13, 01 Jan.

00:06:13, 01 Jan.

00:06:07, 01 Jan.

wl1:A WiFi device <B4:82:FE:BC:18:82> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

00:06:07, 01 Jan.

wl1:A WiFi device <AC:B5:7D:7C:EC:19> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

00:06:07, 01 Jan.

wl0:A WiFi device <C4:73:1E:D4:42:DF> has successfully connected to SSID (Device/WiFi/SSIDs/SSID[WL_PRIV5G])

00:06:07, 01 Jan.

wl1:Device <AC:B5:7D:7C:EC:19> was disconnected on SSID (Device/WiFi/SSIDs/SSID[WL_PRIV2G])

00:05:59, 01 Jan.

:The LAN DHCP Server is inactive

00:05:59, 01 Jan.

:DHCP Confirmation of Request

00:05:59, 01 Jan.

:DHCP Confirmation of Request

00:05:59, 01 Jan.

:DHCP Confirmation of Request

00:05:58, 01 Jan.

wl1:(11/1) Channel Hopping initiated/Manually initiated

00:05:58, 01 Jan.

:DHCP Confirmation of Request

Pl

Re: Issues connecting to my godaddy hosted website trace report shows it reaching a firewall

Re: Issues connecting to my godaddy hosted website trace report shows it reaching a firewall

Re: Issues connecting to my godaddy hosted website trace report shows it reaching a firewall

Re: Issues connecting to my godaddy hosted website trace report shows it reaching a firewall

Re: Issues connecting to my godaddy hosted website trace report shows it reaching a firewall

Re: Issues connecting to my godaddy hosted website trace report shows it reaching a firewall

Re: Issues connecting to my godaddy hosted website trace report shows it reaching a firewall

Re: Issues connecting to my godaddy hosted website trace report shows it reaching a firewall

Re: Issues connecting to my godaddy hosted website trace report shows it reaching a firewall

Re: Issues connecting to my godaddy hosted website trace report shows it reaching a firewall