Re: [squid-users] Unable to access internal resources via hostname

2024-09-30 Thread Piana, Josh
2024 10:51 AM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from outside of Hexcel. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 6/09/24 03

Re: [squid-users] Unable to access internal resources via hostname

2024-09-17 Thread Piana, Josh
--- From: squid-users On Behalf Of Alex Rousskov Sent: Monday, September 16, 2024 11:55 PM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from outside of Hexcel. Do not click links or open attach

Re: [squid-users] Unable to access internal resources via hostname

2024-09-17 Thread Piana, Josh
"why can't I get this to work?" Thank you, Josh -Original Message- From: ngtech1...@gmail.com Sent: Tuesday, September 17, 2024 4:17 AM To: squid-users@lists.squid-cache.org Cc: Piana, Josh Subject: RE: [squid-users] Unable to access internal resources via hostname

Re: [squid-users] Unable to access internal resources via hostname

2024-09-17 Thread ngtech1ltd
for most people. I'll keep looking and see what else could be blocking traffic. -Original Message- From: squid-users On Behalf Of Antony Stone Sent: Monday, September 16, 2024 2:23 PM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resource

Re: [squid-users] Unable to access internal resources via hostname

2024-09-16 Thread Alex Rousskov
uidAcl HTH, Alex. -Original Message- From: squid-users On Behalf Of Alex Rousskov Sent: Monday, September 16, 2024 10:42 AM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from outside o

Re: [squid-users] Unable to access internal resources via hostname

2024-09-16 Thread Amos Jeffries
### # END OF FILE ## -Original Message- From: Alex Rousskov Sent: Monday, September 16, 2024 1:35 PM To: Piana, Josh Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from outsid

Re: [squid-users] Unable to access internal resources via hostname

2024-09-16 Thread Piana, Josh
block traffic. I'll just > take it out if neither of these statements are needed. > > -Original Message- > From: squid-users On > Behalf Of Alex Rousskov > Sent: Monday, September 16, 2024 10:42 AM > To: squid-users@lists.squid-cache.org > Subject: Re: [squid-use

Re: [squid-users] Unable to access internal resources via hostname

2024-09-16 Thread Piana, Josh
I'll keep looking and see what else could be blocking traffic. -Original Message- From: squid-users On Behalf Of Antony Stone Sent: Monday, September 16, 2024 2:23 PM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname [

Re: [squid-users] Unable to access internal resources via hostname

2024-09-16 Thread Antony Stone
On Monday 16 September 2024 at 20:06:41, Piana, Josh wrote: > How I understand the rules are as follows: > > http_access deny !localnet > > This denies HTTP traffic to what I defined as "localnet". No; firstly the "localnet" ACL is defined by *source* address, therefore "localnet" matches traff

Re: [squid-users] Unable to access internal resources via hostname

2024-09-16 Thread Piana, Josh
Sent: Monday, September 16, 2024 10:42 AM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from outside of Hexcel. Do not click links or open attachments unless you recognize the sender and know the

Re: [squid-users] Unable to access internal resources via hostname

2024-09-16 Thread Alex Rousskov
f Of Amos Jeffries Sent: Saturday, September 7, 2024 10:51 AM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from outside of Hexcel. Do not click links or open attachments unless you recognize the sen

Re: [squid-users] Unable to access internal resources via hostname

2024-09-16 Thread Piana, Josh
ginal Message- From: squid-users On Behalf Of Amos Jeffries Sent: Saturday, September 7, 2024 10:51 AM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from outside of Hexcel. Do not click links or

Re: [squid-users] Unable to access internal resources via hostname

2024-09-10 Thread Piana, Josh
0:51 AM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from outside of Hexcel. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 6/09/24 03:56, Pian

Re: [squid-users] Unable to access internal resources via hostname

2024-09-07 Thread Amos Jeffries
On 6/09/24 03:56, Piana, Josh wrote: Hello Amos, While the comments did say that it was just the 10.46.11.0 range, I don't think there's any other ACL forcing that. I tried adding the the two internal sites that are being blocked by their IP, restarted Squid, and tested. Still being blocked. Y

Re: [squid-users] Unable to access internal resources via hostname

2024-09-05 Thread Piana, Josh
le > config that we have has been pieced together and I'd like to get it to the > way it's supposed to be. > > What do you recommend? I can send the whole config again, exactly as we have > it now, and see what we can fix/remove/replace. > > Appreicate you helpin

Re: [squid-users] Unable to access internal resources via hostname

2024-09-05 Thread Piana, Josh
mat custom %tl.%03tu %>a %Ss/%03>Hs % On Behalf Of Amos Jeffries Sent: Wednesday, September 4, 2024 9:23 PM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from outside of Hexcel. Do not click links or

Re: [squid-users] Unable to access internal resources via hostname

2024-09-04 Thread Amos Jeffries
Hi Josh, There are two things I can see in the original message: 1) trusted *clients* (acl authless_src src ...) are documented as being limited to the 10.46.11.0/24 range. The client testing is outside, in the 10.46.49.190 IP address. ==> Please check your authless_src list is correct.

Re: [squid-users] Unable to access internal resources via hostname

2024-09-04 Thread Alex Rousskov
e- From: squid-users On Behalf Of Alex Rousskov Sent: Tuesday, September 3, 2024 4:43 PM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from outside of Hexcel. Do not click links or ope

Re: [squid-users] Unable to access internal resources via hostname

2024-09-04 Thread Piana, Josh
helping us troubleshoot. Respectfully, Josh -Original Message- From: squid-users On Behalf Of Alex Rousskov Sent: Tuesday, September 3, 2024 4:43 PM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email origi

Re: [squid-users] Unable to access internal resources via hostname

2024-09-04 Thread Piana, Josh
xt/html > 29/Aug/2024:10:27:17 -0400.376 10.46.49.190 TCP_DENIED/407 4132 > CONNECT hexcelssp:443 - HIER_NONE/- text/html > 29/Aug/2024:10:27:17 -0400.514 10.46.49.190 NONE_NONE/500 0 CONNECT > hexcelssp:443 JPIANA@AD..COM HIER_NONE/- - > > I'm not sure the debuggin

Re: [squid-users] Unable to access internal resources via hostname

2024-09-04 Thread Piana, Josh
Uh9PWut1%2FyxniOr6l1RL4%3D&reserved=0..com:8080/squid-internal > -static/icons/SN.png - HIER_NONE/- text/html > 29/Aug/2024:10:27:17 -0400.376 10.46.49.190 TCP_DENIED/407 4132 > CONNECT hexcelssp:443 - HIER_NONE/- text/html > 29/Aug/2024:10:27:17 -0400.514 10.46.49.190 NONE_NONE/500 0 C

Re: [squid-users] Unable to access internal resources via hostname

2024-09-03 Thread Alex Rousskov
- HIER_NONE/- text/html 29/Aug/2024:10:27:17 -0400.514 10.46.49.190 NONE_NONE/500 0 CONNECT hexcelssp:443 JPIANA@AD..COM HIER_NONE/- - I'm not sure the debugging and extra log details were added correctly, because these look the same. Thanks, Josh -Original Message- From: squid

Re: [squid-users] Unable to access internal resources via hostname

2024-08-30 Thread Alex Rousskov
- From: squid-users On Behalf Of Alex Rousskov Sent: Thursday, August 29, 2024 2:24 PM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from outside of Hexcel. Do not click links or open attachme

Re: [squid-users] Unable to access internal resources via hostname

2024-08-30 Thread Piana, Josh
enerates HTTP 500 errors for a variety of different reasons. Are >>> there any messages in cache.log (at default debugging level) that >>> correspond to these failing test transactions? If there are none, please >>> add %err_code/%err_detail to your access_log logformat so that Squi

Re: [squid-users] Unable to access internal resources via hostname

2024-08-29 Thread Alex Rousskov
ent: Thursday, August 29, 2024 12:00 PM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from outside of Hexcel. Do not click links or open attachments unless you recognize the sender and know the co

Re: [squid-users] Unable to access internal resources via hostname

2024-08-29 Thread Piana, Josh
tatic/icons/SN.png - HIER_NONE/- text/html > 29/Aug/2024:10:27:17 -0400.376 10.46.49.190 TCP_DENIED/407 4132 > CONNECT hexcelssp:443 - HIER_NONE/- text/html > 29/Aug/2024:10:27:17 -0400.514 10.46.49.190 NONE_NONE/500 0 CONNECT > hexcelssp:443 JPIANA@AD..COM HIER_NONE/- - > > I&#

Re: [squid-users] Unable to access internal resources via hostname

2024-08-29 Thread Alex Rousskov
atures, I'm not familiar with it at all. I apologize for the wall of text, looking forward to what you guys have to say about this. Thanks, Josh -Original Message- From: squid-users On Behalf Of Alex Rousskov Sent: Wednesday, August 28, 2024 2:31 PM To: squid-users@lists.squid-cache.org

Re: [squid-users] Unable to access internal resources via hostname

2024-08-29 Thread Piana, Josh
-Original Message- From: squid-users On Behalf Of Alex Rousskov Sent: Wednesday, August 28, 2024 4:01 PM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from outside of Hexcel. Do not click links or

Re: [squid-users] Unable to access internal resources via hostname

2024-08-28 Thread Alex Rousskov
all. I apologize for the wall of text, looking forward to what you guys have to say about this. Thanks, Josh -Original Message- From: squid-users On Behalf Of Alex Rousskov Sent: Wednesday, August 28, 2024 2:31 PM To: squid-users@lists.squid-cache.org Subject: Re: [squid-user

Re: [squid-users] Unable to access internal resources via hostname

2024-08-28 Thread Matus UHLAR - fantomas
We are unable to get to internal resources via hostname but using the IP address works fine. Immediately, I thought this was DNS but when I checked the /etc/resolv.conf/ file it was pointing correctly to our Windows DNS server and we can ping all devices using their hostname, just not when browsi

Re: [squid-users] Unable to access internal resources via hostname

2024-08-28 Thread Piana, Josh
forward to what you guys have to say about this. Thanks, Josh -Original Message- From: squid-users On Behalf Of Alex Rousskov Sent: Wednesday, August 28, 2024 2:31 PM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Ca

Re: [squid-users] Unable to access internal resources via hostname

2024-08-28 Thread Alex Rousskov
47 AM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from outside of Hexcel. Do not click links or open attachments unless you recognize the sender and know the content is safe. On 28.08.24 14:20, Pia

Re: [squid-users] Unable to access internal resources via hostname

2024-08-28 Thread Alex Rousskov
allow authless_src http_reply_access allow authless_src --- -Original Message- From: squid-users On Behalf Of Matus UHLAR - fantomas Sent: Wednesday, August 28, 2024 10:47 AM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to acce

Re: [squid-users] Unable to access internal resources via hostname

2024-08-28 Thread Piana, Josh
access allow authless_src --- -Original Message- From: squid-users On Behalf Of Matus UHLAR - fantomas Sent: Wednesday, August 28, 2024 10:47 AM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Unable to access internal resources via hostname Caution: This email originated from

Re: [squid-users] Unable to access internal resources via hostname

2024-08-28 Thread Matus UHLAR - fantomas
On 28.08.24 14:20, Piana, Josh wrote: Hello Squid Support, This squid user forum FYI We are unable to get to internal resources via hostname but using the IP address works fine. Immediately, I thought this was DNS but when I checked the /etc/resolv.conf/ file it was pointing correctly to ou

[squid-users] Unable to access internal resources via hostname

2024-08-28 Thread Piana, Josh
Hello Squid Support, We have a newly configured Squid Web Proxy that is allowing connections to external addresses as expected, seemingly following the written ACL's we have in place. We are unable to get to internal resources via hostname but using the IP address works fine. Immediately, I th