|
Perfect, thanks!
I like your bit of hedgehog wisdom. I'm going to impart it on my neighbor
@matthew-dennis
|
|
|
|
|
Hey Jeff,
Can you trying doing a tracert www.codeproject.com to see where the bottleneck is? (only worry about the nodes up until peer1. Everything after that will timeout on purpose)
cheers
Chris Maunder
|
|
|
|
|
Here's what I got:
Microsoft Windows [Version 10.0.19041.746]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\Users\Work>tracert www.codeproject.com
Tracing route to www.codeproject.com [76.74.234.210]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms 192.168.0.1
2 66 ms 66 ms 86 ms br1.grn.acsalaska.net [209.193.63.232]
3 139 ms 140 ms 135 ms ae8-2000-mx1.grn.acsalaska.net [63.140.116.220]
4 182 ms 192 ms 186 ms ae10-r2.nwc.acsalaska.net [63.140.116.68]
5 92 ms 90 ms 90 ms ae9-r2.sea.acsalaska.net [63.140.116.225]
6 92 ms 90 ms 89 ms sea-b2-link.telia.net [213.248.86.126]
7 208 ms 218 ms 203 ms chi-b23-link.ip.twelve99.net [62.115.117.49]
8 175 ms 212 ms 150 ms aptumtech-svc072773-ic360373.c.telia.net [62.115.175.229]
9 204 ms 230 ms 245 ms et-3-0-2.tor-fr709-dis-1.peer1.net [216.187.88.61]
10 203 ms 202 ms 228 ms tor-fr402-xe3-1.peer1.net [216.187.113.86]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
This is from my ISP's network that can reach your server but can't download the file. I called them to discuss their other network that can't reach your server at all, and the tech asked me to bypass the WatchGuard router there, temporarily plug a laptop directly into their switch and manually assign an IP from the range they've allocated. If after that I still can't connect, he suggested the possibility that you may be blocking a range of IPs that includes their range.
Do you have a way to check on this?
In any case, I won't be able to make it over there for such a test for another day or so.
Thanks,
Jeff Bowman
Fairbanks, Alaska
|
|
|
|
|
We can't test anything downstream. My guess: someone or something is blocking us.
Do you have any ad blockers installed (or uBlock?) They play absolute havoc with sites.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: We can't test anything downstream
Sure, I understand. But if your network admins were intentionally blocking an IP range—for whatever reason—wouldn't you be able to find that out?
My network: I use ABP, but I turned it off for CP. Same result (the download starts fine but then incoming packets halt at about 10% complete). I don't use an ad blocker at the other network.
This is really odd, because page loads are just fine. I can download files from other articles lickety-split. It's just this one file from this one article.
Thanks,
Jeff Bowman
Fairbanks, Alaska
modified 17-Feb-21 19:49pm.
|
|
|
|
|
Chris Maunder wrote: We can't test anything downstream
p.s. Not sure what you mean by downstream in this context.
|
|
|
|
|
Sorry: I meant anything outside of our systems we can't test. We can ping / tracert from us to your ISP but that probably won't tell us much. Sounds like there's a block in there somewhere
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: Sounds like there's a block in there somewhere Yes, you're correct. Our WatchGuard firewall appliance was incorrectly blocking the site. Thanks to @jeron1 for assisting with that.
Download attempts for the article's source code are still timing out, though. It starts off like a bull, traffic slows down to fits and starts for a bit, and then everything goes quiet.
Thanks,
Jeff Bowman
Fairbanks, Alaska
|
|
|
|
|
Jeff Bowman wrote: WatchGuard router
Interesting...within the last week CodeProject is blocked at work by the WatchGuard router, they claim that it is being detected as a botnet. I'll have to work on the boss to make the exception.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
We'll ask our IT guys to dig in and see who they need to slap to get this sorted.
cheers
Chris Maunder
|
|
|
|
|
I'm not sure what happened, I've used this site for years at work, then all of the sudden nothing but connection timeouts... Maybe a WatchGuard update botched things up, the fact that someone else had a similar issue seems too coincidental.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
This was exactly the issue. I'm not sure why I didn't think to check for it, so your suggestion was very timely.
I added an exception for *.codeproject.com and all was well.
Thanks,
Jeff Bowman
Fairbanks, Alaska
|
|
|
|
|
Good to hear!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Greg Utas wrote: he'll be told that he was mentioned in a post and will come running to see what the fuss is about. That's discutible
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Message Removed
modified 19-Mar-21 21:01pm.
|
|
|
|
|
The link is now inside the code blocks (I have a feeling it used to be above), with the result that any copied block includes the "Copy Code" text at the beginning.
int main()
{
printf("Hello, world!\n");
}
|
|
|
|
|
That includes using the "Copy Code" button:
Quote: Copy Codeint main()
{
printf("Hello, world!\n");
}
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
All fixed!
cheers
Chris Maunder
|
|
|
|
|
Lots of QA questions explain a problem, then under "What I have tried:" they just repeat the same description.
Suggestion is: replace "What I have tried:" by something more specific that better matches what we want to see there, e.g.
"What I have tried after the problem occurred:"
"My first attempts to solve the problem:"
Luc Pattyn [My Articles]
If you can't find it on YouTube try TikTok...
|
|
|
|
|
From my point of view this "What I have tried" is anyway useless. Some place a copy of the question there others simply fill enough useless characters until post is accepted.
Simply remove that useless "What I have tried"
Only a noob's view.
modified 27-Mar-21 21:01pm.
|
|
|
|
|
No, it does help in some cases. It makes some - not many, not enough - think about the question and put some information in. Before it was there, we got a lot more "My code don't work - fix it?" type than we do now.
Problem is the lazy ones won't read anything in case learning is accidentally imparted ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
My policy would be strict:
1. give clear, concise, unambiguous instructions; improve them when possible.
2. for all: ignore who ignores the instructions, not even a lengthy "Bad question..." response
3. for moderators: do not remove but respond with exactly one sentence "bad question, to be ignored" (*), remove any other response that may appear, and freeze the question, thus preventing further edits/comments/answers/solutions. Offenders should not be rewarded! They don't deserve a second of our attention.
(*) make this a link to a lengthy page that explains what good and bad questions are
Luc Pattyn [My Articles]
If you can't find it on YouTube try TikTok...
|
|
|
|
|
But the main problem is not that people ignore the instructions, they do not bother to read them. And far too many just do not know how to ask a question. One of the most common questions is "It does not work, please fix it". So however hard Chris and the team work to make it easy to post a question, add full details and nice neatly formatted code, people will still do what they think is enough.
|
|
|
|
|
And then we ignore them, as there is no alternative.
Luc Pattyn [My Articles]
If you can't find it on YouTube try TikTok...
|
|
|
|
|
well, as Chris says, we should try to help everybody, even those who appear to be useless or lazy. At the very least we can tell them why they are not getting the answer they expect.
|
|
|
|