Help with web site

It's not much solace for being unable to get your site to work, but browsing the subforum tonight was the first time I discovered your site. I'm happy so say not only will I be a customer, but your blem prices are so exceptional I'll be a customer sooner than I could have anticipated :D Also, I'd never really thought about blems before, but I'm a definition user and I'm now excited to order soon.
 
Worked perfectly from my mobile.

If only i had more money at the moment....darn.
 
Kershawguy.com working alright.
There's no other place to get a Kershaw & ZT except from kershawguy.com:thumbup:
 
Hopefully this helps, though I am not sure how much can be done other than to contact the hosting company and see what they say. Please pardon any lingo or weird terms I might use. Also, this is more tech than knives, but maybe it will be of some use.

I can reach your site from home with no problem.

This kind of issue is indicative of a high level routing issue on the internet between CenturyLink (or one of their carriers) and your hosting site's carriers. I see this from time to time in my work.

I did a traceroute from me to your site to learn the path and determine your hosting company.

My path to you eventually reaches IP address 174.127.131.66 which is registered to Vanoppen.biz LLC (AKA Spectrum Networks) in Seattle.

From Vanoppen, it goes to IP 66.171.176.13 which is registered to Atlas Networks, also of Seattle.

From there to your hosting server at into9.funseattlenights.com [76.191.127.138].

Since Atlas is apparently a hosting firm, I assume they have multiple redundant carrier connections. They do not, at least not according to Hurricane Electric's BGP (internet routing protocol) tracking tool. http://bgp.he.net/AS21743

For all I know Vanoppen and Atlas could be one and the same from a business perspective.

They have one peer to Vanoppen.biz. Vanoppen has at least 10 peers on the internet for redundancy. http://bgp.he.net/AS11404. CenturyLink's Looking Glass (BGP testing tool) using a core router in Spokane (SPK2, via the tool at https://kai04.centurylink.com/PtapRpts/Public/BackboneReport.aspx) indicates their path to your server is via Qwest. CenturyLink and Qwest merged, and they are still combining their infrastructures, I am sure.

Quest is one of Vanoppen's peers. Without knowing more information, my best guess is a flaky BGP or even physical connection between Qwest and Vanoppen, making CenturyLink initiated connections fail to connect periodically. Any other hosting providers having trouble getting to your site? At the moment, the SPK2 CenturyLink router thinks it can reach your site (using the same CenturyLink tool that I mentioned above to ping the server, but not via traceroute).
 
MrFoo said:
Hopefully this helps, though I am not sure how much can be done other than to contact the hosting company and see what they say. Please pardon any lingo or weird terms I might use. Also, this is more tech than knives, but maybe it will be of some use.

I can reach your site from home with no problem.

This kind of issue is indicative of a high level routing issue on the internet between CenturyLink (or one of their carriers) and your hosting site's carriers. I see this from time to time in my work.

I did a traceroute from me to your site to learn the path and determine your hosting company.

My path to you eventually reaches IP address 174.127.131.66 which is registered to Vanoppen.biz LLC (AKA Spectrum Networks) in Seattle.

From Vanoppen, it goes to IP 66.171.176.13 which is registered to Atlas Networks, also of Seattle.

From there to your hosting server at into9.funseattlenights.com [76.191.127.138].

Since Atlas is apparently a hosting firm, I assume they have multiple redundant carrier connections. They do not, at least not according to Hurricane Electric's BGP (internet routing protocol) tracking tool. http://bgp.he.net/AS21743

For all I know Vanoppen and Atlas could be one and the same from a business perspective.

They have one peer to Vanoppen.biz. Vanoppen has at least 10 peers on the internet for redundancy. http://bgp.he.net/AS11404. CenturyLink's Looking Glass (BGP testing tool) using a core router in Spokane (SPK2, via the tool at https://kai04.centurylink.com/PtapRpts/Public/BackboneReport.aspx) indicates their path to your server is via Qwest. CenturyLink and Qwest merged, and they are still combining their infrastructures, I am sure.

Quest is one of Vanoppen's peers. Without knowing more information, my best guess is a flaky BGP or even physical connection between Qwest and Vanoppen, making CenturyLink initiated connections fail to connect periodically. Any other hosting providers having trouble getting to your site? At the moment, the SPK2 CenturyLink router thinks it can reach your site (using the same CenturyLink tool that I mentioned above to ping the server, but not via traceroute).
Click to expand...

Ok , well I don't understand most of that , but I am going to forward this info to my web guy and it may be helpful to him. Thank You.
 
I know that I got the acknowledgement for a number of orders at least a week after I'd received them from you, which seemed a bit odd. If you're on the same LAN as your site there might be a constraint on your ability to reach that site using an external address. That happens to me sometimes on web pages that I have on a little Apache server. (I think it's called "loop back.")
 
freewheeling said:
I know that I got the acknowledgement for a number of orders at least a week after I'd received them from you, which seemed a bit odd. If you're on the same LAN as your site there might be a constraint on your ability to reach that site using an external address. That happens to me sometimes on web pages that I have on a little Apache server. (I think it's called "loop back.")
Click to expand...

That is a different problem I am having with IPN payment notification, all my orders since 12/28 show incomplete and I doubt any of those folks received notification of purchase, still trying to figure that one out too.
 
You must log in or register to reply here.
Back
Top