Quantcast

Unable to forward this request at this time.

classic Classic list List threaded Threaded
23 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Unable to forward this request at this time.

Die~~ ٩๏̯͡๏۶ ̿ ̿ ̿ ̿ ̿̿’\̵͇̿̿\=(•̪●)‏ ɹɐzǝupɐɥʞ ɐzɹıɯ
i cant browse from outside and local
----
ERROR
The requested URL could not be retrieved

While trying to retrieve the URL: http://monitor.gpi-g.com/

The following error was encountered:

    * Unable to forward this request at this time.

This request could not be forwarded to the origin server or to any
parent caches. The most likely cause for this error is that:

    * The cache administrator does not allow this cache to make direct
connections to origin servers, and
    * All configured parent caches are currently unreachable.

Your cache administrator is [hidden email].
Generated Mon, 10 Nov 2008 03:18:16 GMT by gpi-g.com (squid/2.6.STABLE18)
----


--
-=-=-=-=
http://amyhost.com
Dollar naik ? Krisis ? Kami tetap mempertahankan harga jual domain Rp.
75.000 rupiah
------------
Pengin punya Layanan SMS PREMIUM ?
Contact me ASAP. dapatkan Share revenue MAXIMAL tanpa syarat traffic...
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Amos Jeffries-2
??? ??z?up??? ?z??? ??? wrote:

> i cant browse from outside and local
> ----
> ERROR
> The requested URL could not be retrieved
>
> While trying to retrieve the URL: http://monitor.gpi-g.com/
>
> The following error was encountered:
>
>     * Unable to forward this request at this time.
>
> This request could not be forwarded to the origin server or to any
> parent caches. The most likely cause for this error is that:
>
>     * The cache administrator does not allow this cache to make direct
> connections to origin servers, and
>     * All configured parent caches are currently unreachable.
>
> Your cache administrator is [hidden email].
> Generated Mon, 10 Nov 2008 03:18:16 GMT by gpi-g.com (squid/2.6.STABLE18)
> ----
>
>

So it seems.

Check your squid configuration and Internet connection.

Amos
--
Please be using
   Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
   Current Beta Squid 3.1.0.1
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Die~~ ٩๏̯͡๏۶ ̿ ̿ ̿ ̿ ̿̿’\̵͇̿̿\=(•̪●)‏ ɹɐzǝupɐɥʞ ɐzɹıɯ
my squid working for other site :(
fyi :
my public IP 202.169.51.118
and monitor.gpi-g.com is 202.169.51.118 too

and i can browse mail.gpi-g.com - 202.169.51.119
( same server farm with different server - one line/level with 118 )

On Mon, Nov 10, 2008 at 11:21 AM, Amos Jeffries <[hidden email]> wrote:

> ??? ??z?up??? ?z??? ??? wrote:
>>
>> i cant browse from outside and local
>> ----
>> ERROR
>> The requested URL could not be retrieved
>>
>> While trying to retrieve the URL: http://monitor.gpi-g.com/
>>
>> The following error was encountered:
>>
>>    * Unable to forward this request at this time.
>>
>> This request could not be forwarded to the origin server or to any
>> parent caches. The most likely cause for this error is that:
>>
>>    * The cache administrator does not allow this cache to make direct
>> connections to origin servers, and
>>    * All configured parent caches are currently unreachable.
>>
>> Your cache administrator is [hidden email].
>> Generated Mon, 10 Nov 2008 03:18:16 GMT by gpi-g.com (squid/2.6.STABLE18)
>> ----
>>
>>
>
> So it seems.
>
> Check your squid configuration and Internet connection.
>
> Amos
> --
> Please be using
>  Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
>  Current Beta Squid 3.1.0.1
>



--
-=-=-=-=
http://amyhost.com
Dollar naik ? Krisis ? Kami tetap mempertahankan harga jual domain Rp.
75.000 rupiah
------------
Pengin punya Layanan SMS PREMIUM ?
Contact me ASAP. dapatkan Share revenue MAXIMAL tanpa syarat traffic...
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Amos Jeffries-2
??? ??z?up??? ?z??? ??? wrote:
> my squid working for other site :(
> fyi :
> my public IP 202.169.51.118
> and monitor.gpi-g.com is 202.169.51.118 too
>
> and i can browse mail.gpi-g.com - 202.169.51.119
> ( same server farm with different server - one line/level with 118 )

Then it's probably a configuration problem.
By your description (IPs the same) your squid is supposed to be an
accelerator for that website. Which means the cache_peer configuration
needs to be checked.

Amos

>
> On Mon, Nov 10, 2008 at 11:21 AM, Amos Jeffries <[hidden email]> wrote:
>> ??? ??z?up??? ?z??? ??? wrote:
>>> i cant browse from outside and local
>>> ----
>>> ERROR
>>> The requested URL could not be retrieved
>>>
>>> While trying to retrieve the URL: http://monitor.gpi-g.com/
>>>
>>> The following error was encountered:
>>>
>>>    * Unable to forward this request at this time.
>>>
>>> This request could not be forwarded to the origin server or to any
>>> parent caches. The most likely cause for this error is that:
>>>
>>>    * The cache administrator does not allow this cache to make direct
>>> connections to origin servers, and
>>>    * All configured parent caches are currently unreachable.
>>>
>>> Your cache administrator is [hidden email].
>>> Generated Mon, 10 Nov 2008 03:18:16 GMT by gpi-g.com (squid/2.6.STABLE18)
>>> ----
>>>
>>>
>> So it seems.
>>
>> Check your squid configuration and Internet connection.
>>
>> Amos
>> --
>> Please be using
>>  Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
>>  Current Beta Squid 3.1.0.1
>>
>
>
>


--
Please be using
   Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
   Current Beta Squid 3.1.0.1
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Die~~ ٩๏̯͡๏۶ ̿ ̿ ̿ ̿ ̿̿’\̵͇̿̿\=(•̪●)‏ ɹɐzǝupɐɥʞ ɐzɹıɯ
here is my squid .conf
===========
http_port 2210 transparent
icp_port 3130
snmp_port 3401
cache_mgr admin
emulate_httpd_log off
cache_replacement_policy heap LFUDA
maximum_object_size_in_memory 50 KB
maximum_object_size 50 MB

http_port 80 accel defaultsite=monitor.gpi-g.com
cache_peer 202.169.51.118 parent 80 0 no-query originserver name=myAccel
acl our_sites dstdomain monitor.gpi-g.com
http_access allow our_sites
cache_peer_access myAccel allow our_sites

dead_peer_timeout 10 seconds
acl QUERY urlpath_regex cgi-bin \?
no_cache deny QUERY
visible_hostname gpi-g.com
cache_mem 5 MB
memory_pools off
log_icp_queries on
buffered_logs on
quick_abort_min 0 KB
quick_abort_max 0 KB
quick_abort_pct 95
cache_swap_low 70%
cache_swap_high 90%
cache_dir aufs /var/spool/squid 4000 16 256
cache_dir aufs /var/spool/squid1 4000 16 256
cache_dir aufs /var/spool/squid2 4000 16 256
cache_dir aufs /var/spool/squid3 4000 16 256
cache_access_log /var/log/squid/access.log
cache_log /var/log/squid/cache.log
cache_store_log /var/log/squid/store.log
pid_filename /var/run/squid.pid
forwarded_for on
half_closed_clients off

cache_effective_user proxy
cache_effective_group proxy
cache_mgr [hidden email]
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern . 0 20% 4320

....[cut]
===========================

On Mon, Nov 10, 2008 at 11:28 AM, Amos Jeffries <[hidden email]> wrote:

> ??? ??z?up??? ?z??? ??? wrote:
>>
>> my squid working for other site :(
>> fyi :
>> my public IP 202.169.51.118
>> and monitor.gpi-g.com is 202.169.51.118 too
>>
>> and i can browse mail.gpi-g.com - 202.169.51.119
>> ( same server farm with different server - one line/level with 118 )
>
> Then it's probably a configuration problem.
> By your description (IPs the same) your squid is supposed to be an
> accelerator for that website. Which means the cache_peer configuration needs
> to be checked.
>
> Amos
>
>>
>> On Mon, Nov 10, 2008 at 11:21 AM, Amos Jeffries <[hidden email]>
>> wrote:
>>>
>>> ??? ??z?up??? ?z??? ??? wrote:
>>>>
>>>> i cant browse from outside and local
>>>> ----
>>>> ERROR
>>>> The requested URL could not be retrieved
>>>>
>>>> While trying to retrieve the URL: http://monitor.gpi-g.com/
>>>>
>>>> The following error was encountered:
>>>>
>>>>   * Unable to forward this request at this time.
>>>>
>>>> This request could not be forwarded to the origin server or to any
>>>> parent caches. The most likely cause for this error is that:
>>>>
>>>>   * The cache administrator does not allow this cache to make direct
>>>> connections to origin servers, and
>>>>   * All configured parent caches are currently unreachable.
>>>>
>>>> Your cache administrator is [hidden email].
>>>> Generated Mon, 10 Nov 2008 03:18:16 GMT by gpi-g.com
>>>> (squid/2.6.STABLE18)
>>>> ----
>>>>
>>>>
>>> So it seems.
>>>
>>> Check your squid configuration and Internet connection.
>>>
>>> Amos
>>> --
>>> Please be using
>>>  Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
>>>  Current Beta Squid 3.1.0.1
>>>
>>
>>
>>
>
>
> --
> Please be using
>  Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
>  Current Beta Squid 3.1.0.1
>



--
-=-=-=-=
http://amyhost.com
Dollar naik ? Krisis ? Kami tetap mempertahankan harga jual domain Rp.
75.000 rupiah
------------
Pengin punya Layanan SMS PREMIUM ?
Contact me ASAP. dapatkan Share revenue MAXIMAL tanpa syarat traffic...
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Henrik Nordström
From the error it sounds like it has declared the peer down.

On mån, 2008-11-10 at 11:35 +0700, ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

> here is my squid .conf
> ===========
> http_port 2210 transparent
> icp_port 3130
> snmp_port 3401
> cache_mgr admin
> emulate_httpd_log off
> cache_replacement_policy heap LFUDA
> maximum_object_size_in_memory 50 KB
> maximum_object_size 50 MB
>
> http_port 80 accel defaultsite=monitor.gpi-g.com
> cache_peer 202.169.51.118 parent 80 0 no-query originserver name=myAccel
> acl our_sites dstdomain monitor.gpi-g.com
> http_access allow our_sites
> cache_peer_access myAccel allow our_sites
>
> dead_peer_timeout 10 seconds
> acl QUERY urlpath_regex cgi-bin \?
> no_cache deny QUERY
> visible_hostname gpi-g.com
> cache_mem 5 MB
> memory_pools off
> log_icp_queries on
> buffered_logs on
> quick_abort_min 0 KB
> quick_abort_max 0 KB
> quick_abort_pct 95
> cache_swap_low 70%
> cache_swap_high 90%
> cache_dir aufs /var/spool/squid 4000 16 256
> cache_dir aufs /var/spool/squid1 4000 16 256
> cache_dir aufs /var/spool/squid2 4000 16 256
> cache_dir aufs /var/spool/squid3 4000 16 256
> cache_access_log /var/log/squid/access.log
> cache_log /var/log/squid/cache.log
> cache_store_log /var/log/squid/store.log
> pid_filename /var/run/squid.pid
> forwarded_for on
> half_closed_clients off
>
> cache_effective_user proxy
> cache_effective_group proxy
> cache_mgr [hidden email]
> refresh_pattern ^ftp: 1440 20% 10080
> refresh_pattern ^gopher: 1440 0% 1440
> refresh_pattern . 0 20% 4320
>
> ....[cut]
> ===========================
>
> On Mon, Nov 10, 2008 at 11:28 AM, Amos Jeffries <[hidden email]> wrote:
> > ??? ??z?up??? ?z??? ??? wrote:
> >>
> >> my squid working for other site :(
> >> fyi :
> >> my public IP 202.169.51.118
> >> and monitor.gpi-g.com is 202.169.51.118 too
> >>
> >> and i can browse mail.gpi-g.com - 202.169.51.119
> >> ( same server farm with different server - one line/level with 118 )
> >
> > Then it's probably a configuration problem.
> > By your description (IPs the same) your squid is supposed to be an
> > accelerator for that website. Which means the cache_peer configuration needs
> > to be checked.
> >
> > Amos
> >
> >>
> >> On Mon, Nov 10, 2008 at 11:21 AM, Amos Jeffries <[hidden email]>
> >> wrote:
> >>>
> >>> ??? ??z?up??? ?z??? ??? wrote:
> >>>>
> >>>> i cant browse from outside and local
> >>>> ----
> >>>> ERROR
> >>>> The requested URL could not be retrieved
> >>>>
> >>>> While trying to retrieve the URL: http://monitor.gpi-g.com/
> >>>>
> >>>> The following error was encountered:
> >>>>
> >>>>   * Unable to forward this request at this time.
> >>>>
> >>>> This request could not be forwarded to the origin server or to any
> >>>> parent caches. The most likely cause for this error is that:
> >>>>
> >>>>   * The cache administrator does not allow this cache to make direct
> >>>> connections to origin servers, and
> >>>>   * All configured parent caches are currently unreachable.
> >>>>
> >>>> Your cache administrator is [hidden email].
> >>>> Generated Mon, 10 Nov 2008 03:18:16 GMT by gpi-g.com
> >>>> (squid/2.6.STABLE18)
> >>>> ----
> >>>>
> >>>>
> >>> So it seems.
> >>>
> >>> Check your squid configuration and Internet connection.
> >>>
> >>> Amos
> >>> --
> >>> Please be using
> >>>  Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
> >>>  Current Beta Squid 3.1.0.1
> >>>
> >>
> >>
> >>
> >
> >
> > --
> > Please be using
> >  Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
> >  Current Beta Squid 3.1.0.1
> >
>
>
>

signature.asc (316 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Amos Jeffries-2
Henrik Nordstrom wrote:
> From the error it sounds like it has declared the peer down.

But why? I'm thinking forwarding loops.

>
> On mån, 2008-11-10 at 11:35 +0700, ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:
>> here is my squid .conf
>> ===========
>> http_port 2210 transparent
>> icp_port 3130
>> snmp_port 3401
>> cache_mgr admin
>> emulate_httpd_log off
>> cache_replacement_policy heap LFUDA
>> maximum_object_size_in_memory 50 KB
>> maximum_object_size 50 MB
>>
>> http_port 80 accel defaultsite=monitor.gpi-g.com
>> cache_peer 202.169.51.118 parent 80 0 no-query originserver name=myAccel

  ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░   you said:
 >>>> my public IP 202.169.51.118
 >>>> and monitor.gpi-g.com is 202.169.51.118 too

What is Squid IP?

Is web server actually running on 202.169.51.118:80?


<snip>

>>
>> On Mon, Nov 10, 2008 at 11:28 AM, Amos Jeffries <[hidden email]> wrote:
>>> ??? ??z?up??? ?z??? ??? wrote:
>>>> my squid working for other site :(
>>>> fyi :
>>>> my public IP 202.169.51.118
>>>> and monitor.gpi-g.com is 202.169.51.118 too
>>>>
>>>> and i can browse mail.gpi-g.com - 202.169.51.119
>>>> ( same server farm with different server - one line/level with 118 )
>>> Then it's probably a configuration problem.
>>> By your description (IPs the same) your squid is supposed to be an
>>> accelerator for that website. Which means the cache_peer configuration needs
>>> to be checked.
>>>
>>> Amos
>>>
>>>> On Mon, Nov 10, 2008 at 11:21 AM, Amos Jeffries <[hidden email]>
>>>> wrote:
>>>>> ??? ??z?up??? ?z??? ??? wrote:
>>>>>> i cant browse from outside and local
>>>>>> ----
>>>>>> ERROR
>>>>>> The requested URL could not be retrieved
>>>>>>
>>>>>> While trying to retrieve the URL: http://monitor.gpi-g.com/
>>>>>>
>>>>>> The following error was encountered:
>>>>>>
>>>>>>   * Unable to forward this request at this time.
>>>>>>
>>>>>> This request could not be forwarded to the origin server or to any
>>>>>> parent caches. The most likely cause for this error is that:
>>>>>>
>>>>>>   * The cache administrator does not allow this cache to make direct
>>>>>> connections to origin servers, and
>>>>>>   * All configured parent caches are currently unreachable.
>>>>>>
>>>>>> Your cache administrator is [hidden email].
>>>>>> Generated Mon, 10 Nov 2008 03:18:16 GMT by gpi-g.com
>>>>>> (squid/2.6.STABLE18)
>>>>>> ----
>>>>>>
>>>>>>
>>>>> So it seems.
>>>>>
>>>>> Check your squid configuration and Internet connection.
>>>>>
>>>>> Amos
>>>>> --
>>>>> Please be using
>>>>>  Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
>>>>>  Current Beta Squid 3.1.0.1
>>>>>
>>>>
>>>>
>>>
>>> --
>>> Please be using
>>>  Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
>>>  Current Beta Squid 3.1.0.1
>>>
>>
>>


--
Please be using
   Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
   Current Beta Squid 3.1.0.1
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Henrik Nordström
On tis, 2008-11-11 at 03:14 +1300, Amos Jeffries wrote:
> Henrik Nordstrom wrote:
> > From the error it sounds like it has declared the peer down.
>
> But why? I'm thinking forwarding loops.

Forwarding loops is logged very aggressively in cache.log as such, and
don't result in an error to the user. All Squid does on a forwarding
loop is to try to go direct to the origin.

The error message seen here was "Unable to forward" which means that
never_direct is in effect (on by default on accelerated requests), and
that it did not find a parent where to forward the request.

Regards
Henrik

signature.asc (316 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Die~~ ٩๏̯͡๏۶ ̿ ̿ ̿ ̿ ̿̿’\̵͇̿̿\=(•̪●)‏ ɹɐzǝupɐɥʞ ɐzɹıɯ
all :
it's works now
but from Internal
from External ( internet ) it's look like Domain without any space hosting

i remove :
> http_port 80 accel defaultsite=monitor.gpi-g.com
> cache_peer 202.169.51.118 parent 80 0 no-query originserver name=myAccel
> acl our_sites dstdomain monitor.gpi-g.com
> http_access allow our_sites
> cache_peer_access myAccel allow our_sites


to amos :
My squid address = 192.168.222.2 <-- to the lan
202.169.51.118 <-- my public ip
same machine



On Mon, Nov 10, 2008 at 9:47 PM, Henrik Nordstrom
<[hidden email]> wrote:

> On tis, 2008-11-11 at 03:14 +1300, Amos Jeffries wrote:
>> Henrik Nordstrom wrote:
>> > From the error it sounds like it has declared the peer down.
>>
>> But why? I'm thinking forwarding loops.
>
> Forwarding loops is logged very aggressively in cache.log as such, and
> don't result in an error to the user. All Squid does on a forwarding
> loop is to try to go direct to the origin.
>
> The error message seen here was "Unable to forward" which means that
> never_direct is in effect (on by default on accelerated requests), and
> that it did not find a parent where to forward the request.
>
> Regards
> Henrik
>



--
-=-=-=-=
http://amyhost.com
Dollar naik ? Krisis ? Kami tetap mempertahankan harga jual domain Rp.
75.000 rupiah
------------
Pengin punya Layanan SMS PREMIUM ?
Contact me ASAP. dapatkan Share revenue MAXIMAL tanpa syarat traffic...
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Amos Jeffries-2
> all :
> it's works now
> but from Internal
> from External ( internet ) it's look like Domain without any space hosting
>
> i remove :
>> http_port 80 accel defaultsite=monitor.gpi-g.com
>> cache_peer 202.169.51.118 parent 80 0 no-query originserver name=myAccel
>> acl our_sites dstdomain monitor.gpi-g.com
>> http_access allow our_sites
>> cache_peer_access myAccel allow our_sites
>
>
> to amos :
> My squid address = 192.168.222.2 <-- to the lan
> 202.169.51.118 <-- my public ip
> same machine
>

Ahh okay. "cache_peer 202.169.51.118" should be the web server IP as seen
from Squid (internal IP if squid is internal, external IP if squid is
external, localhost maybe if squid is on same machine).

Amos

>
>
> On Mon, Nov 10, 2008 at 9:47 PM, Henrik Nordstrom
> <[hidden email]> wrote:
>> On tis, 2008-11-11 at 03:14 +1300, Amos Jeffries wrote:
>>> Henrik Nordstrom wrote:
>>> > From the error it sounds like it has declared the peer down.
>>>
>>> But why? I'm thinking forwarding loops.
>>
>> Forwarding loops is logged very aggressively in cache.log as such, and
>> don't result in an error to the user. All Squid does on a forwarding
>> loop is to try to go direct to the origin.
>>
>> The error message seen here was "Unable to forward" which means that
>> never_direct is in effect (on by default on accelerated requests), and
>> that it did not find a parent where to forward the request.
>>
>> Regards
>> Henrik
>>
>
>
>
> --
> -=-=-=-=
> http://amyhost.com
> Dollar naik ? Krisis ? Kami tetap mempertahankan harga jual domain Rp.
> 75.000 rupiah
> ------------
> Pengin punya Layanan SMS PREMIUM ?
> Contact me ASAP. dapatkan Share revenue MAXIMAL tanpa syarat traffic...
>


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Die~~ ٩๏̯͡๏۶ ̿ ̿ ̿ ̿ ̿̿’\̵͇̿̿\=(•̪●)‏ ɹɐzǝupɐɥʞ ɐzɹıɯ
On Tue, Nov 11, 2008 at 9:31 AM, Amos Jeffries <[hidden email]> wrote:
>
>
> Ahh okay. "cache_peer 202.169.51.118" should be the web server IP as seen
> from Squid (internal IP if squid is internal, external IP if squid is
> external, localhost maybe if squid is on same machine).
>
> Amos
>

so i should to change it to local ip ? or what ?

------------
Pengin punya Layanan SMS PREMIUM ?
Contact me ASAP. dapatkan Share revenue MAXIMAL tanpa syarat traffic...
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Amos Jeffries-2
░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:

> On Tue, Nov 11, 2008 at 9:31 AM, Amos Jeffries <[hidden email]> wrote:
>>
>> Ahh okay. "cache_peer 202.169.51.118" should be the web server IP as seen
>> from Squid (internal IP if squid is internal, external IP if squid is
>> external, localhost maybe if squid is on same machine).
>>
>> Amos
>>
>
> so i should to change it to local ip ? or what ?
>

Probably. You are the only one who knows what network IPs are directly
routable from your Squid.


Amos
--
Please be using
   Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
   Current Beta Squid 3.1.0.2
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Die~~ ٩๏̯͡๏۶ ̿ ̿ ̿ ̿ ̿̿’\̵͇̿̿\=(•̪●)‏ ɹɐzǝupɐɥʞ ɐzɹıɯ
it;'s works now
i dont know why
but i do reinstall my ubuntu
perhaps something wrong with apache

sorry and thankyou

btw amos can i sent you private email about my config ? squid.conf
tell me it's optimal or not
if you allow me to sent you email
i will put it as a attchment

On Tue, Nov 11, 2008 at 5:29 PM, Amos Jeffries <[hidden email]> wrote:

> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:
>>
>> On Tue, Nov 11, 2008 at 9:31 AM, Amos Jeffries <[hidden email]>
>> wrote:
>>>
>>> Ahh okay. "cache_peer 202.169.51.118" should be the web server IP as seen
>>> from Squid (internal IP if squid is internal, external IP if squid is
>>> external, localhost maybe if squid is on same machine).
>>>
>>> Amos
>>>
>>
>> so i should to change it to local ip ? or what ?
>>
>
> Probably. You are the only one who knows what network IPs are directly
> routable from your Squid.
>
>
> Amos
> --
> Please be using
>  Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
>  Current Beta Squid 3.1.0.2
>



--
-=-=-=-=
http://amyhost.com
Dollar naik ? Krisis ? Kami tetap mempertahankan harga jual domain Rp.
75.000 rupiah
------------
Pengin punya Layanan SMS PREMIUM ?
Contact me ASAP. dapatkan Share revenue MAXIMAL tanpa syarat traffic...
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Amos Jeffries-2
> it;'s works now
> i dont know why
> but i do reinstall my ubuntu
> perhaps something wrong with apache
>
> sorry and thankyou
>
> btw amos can i sent you private email about my config ? squid.conf
> tell me it's optimal or not
> if you allow me to sent you email
> i will put it as a attchment

You should be able to send me email. If you get a blocked message you have
bigger problems that need sorting out as mentioned in the blocking.

Amos

>
> On Tue, Nov 11, 2008 at 5:29 PM, Amos Jeffries <[hidden email]>
> wrote:
>> ░▒▓ ɹɐzǝupɐɥʞ ɐzɹıɯ ▓▒░ wrote:
>>>
>>> On Tue, Nov 11, 2008 at 9:31 AM, Amos Jeffries <[hidden email]>
>>> wrote:
>>>>
>>>> Ahh okay. "cache_peer 202.169.51.118" should be the web server IP as
>>>> seen
>>>> from Squid (internal IP if squid is internal, external IP if squid is
>>>> external, localhost maybe if squid is on same machine).
>>>>
>>>> Amos
>>>>
>>>
>>> so i should to change it to local ip ? or what ?
>>>
>>
>> Probably. You are the only one who knows what network IPs are directly
>> routable from your Squid.
>>
>>
>> Amos
>> --
>> Please be using
>>  Current Stable Squid 2.7.STABLE5 or 3.0.STABLE10
>>  Current Beta Squid 3.1.0.2
>>
>
>
>
> --
> -=-=-=-=
> http://amyhost.com
> Dollar naik ? Krisis ? Kami tetap mempertahankan harga jual domain Rp.
> 75.000 rupiah
> ------------
> Pengin punya Layanan SMS PREMIUM ?
> Contact me ASAP. dapatkan Share revenue MAXIMAL tanpa syarat traffic...
>


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Luc Igert
In reply to this post by Henrik Nordström
Hello,
i'm bumping here because I have the same error message and it is very confusing (at least for me :-) .

I have 3 hosts, my first one (and default) is working without any problem, but the 2 other ones arent.
My hosts are online (I can access the servers per IP).
Is something missing in my .conf?

I'm posting my whole squid.conf, maybe someone just sees where the problem is....
Thanks .


Luc.


Here is my conf:

always_direct allow all
acl manager proto cache_object
acl localhost src 127.0.0.1/32
acl localhost src ::1/128
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1/128
acl localnet src 172.17.0.0/255.255.0.0
acl all src
acl SSL_ports port 443
acl Safe_ports port 80          # http
acl Safe_ports port 21          # ftp
acl Safe_ports port 443         # https
acl Safe_ports port 70          # gopher
acl Safe_ports port 210         # wais
acl Safe_ports port 1025-65535  # unregistered ports
acl Safe_ports port 280         # http-mgmt
acl Safe_ports port 488         # gss-http
acl Safe_ports port 591         # filemakerhttp://XXX.ch/
acl Safe_ports port 777         # multiling http
acl CONNECT method CONNECT

http_access allow manager localhost
http_access allow manager localnet
http_access allow localnet
http_access allow localhost
http_access allow manager
http_access deny !Safe_ports


refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
refresh_pattern . 0 20% 4320


http_port 80 accel defaultsite=backup.XXX.ch vhost
forwarded_for on
cache_peer 172.17.2.30 parent 80 0 no-query no-digest originserver name=mysite1
cache_peer 172.17.2.32 parent 80 0 no-query no-digest originserver name=mysite2
cache_peer 172.17.2.116 parent 80 0 no-query no-digest originserver name=mysite3

cache_peer_domain mysite1 www.XXX.ch
cache_peer_domain mysite2 wbbltest.XXX.ch
cache_peer_domain mysite3 backup.XXX.ch


acl my_site1 dstdomain www.XXX.ch
acl my_site2 dstdomain wbbltest.XXX.ch
acl my_site3 dstdomain backup.XXX.ch
acl myaccelport port 80
acl myaccelport2 port 8080

http_access allow my_site1 myaccelport
http_access allow my_site2 myaccelport
http_access allow my_site3 myaccelport2


http_access deny all




Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Amos Jeffries-2
On 26/01/2012 2:34 a.m., Luc Igert wrote:
> Hello,
> i'm bumping here because I have the same error message and it is very
> confusing (at least for me :-) .

What is more confusing, the error message words or why they are appearing?

>
> I have 3 hosts, my first one (and default) is working without any problem,
> but the 2 other ones arent.
> My hosts are online (I can access the servers per IP).
> Is something missing in my .conf?

Yes. Details below.

>
> I'm posting my whole squid.conf, maybe someone just sees where the problem
> is....
> Thanks .
>
>
> Luc.
>
>
> Here is my conf:
>
> always_direct allow all

This line essentially means "cache_peer lines are to be ignored.".

Squid will lookup DNS records for the domain it is handed and pass the
request DIRECT-ly to the origin server IP it finds there, bypassing the
cache_peer hierarchy.


Amos
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Luc Igert
Hi Amos, and thanks a lot for your answer.I Forgot to say I’m running as a Reverse Proxy with multiple backends, Squid 3.1

What’s  confusing for me is the fact that www.xxx.ch is working, while backup.xxx.ch or wbbltest.xxx.ch aren’t.

I haven’t done anything special on DNS Side, all three subdomains are hosted on the same Public IP and nslookup is giving me the right public ip for every subdomain.

I did remove the always_direct allow all, but I still have the same problem.

Funny thing though: If I change the default website in http_port 80 accel for backup.xxx instead of www.xxx, I still have only www.xxx working…

Is it possible the cache from Squid is full because I didn’t specify how big it is/can be?
Other question : if it passes directly to the origin servers (for instance wbbltest 172.17.2.32), shouldn’t I be able to access the site?

Thanks a lot.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Henrik Nordström
ons 2012-01-25 klockan 08:50 -0800 skrev Luc Igert:
> Hi Amos, and thanks a lot for your answer.I Forgot to say I’m running as a
> Reverse Proxy with multiple backends, Squid 3.1
>
> What’s  confusing for me is the fact that www.xxx.ch is working, while
> backup.xxx.ch or wbbltest.xxx.ch aren’t.

So what cache_peer and cache_peer_access/cache_peer_domain rules do you
have?

You get this error if Squid can not find any acceptable cache_peer to
forward the request to, i.e. no alive cache_peer where
cache_peer_access/cache_peer_domain says it can forward the request.

Regards
Henrik

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Amos Jeffries-2
On 26.01.2012 13:21, Henrik Nordström wrote:

> ons 2012-01-25 klockan 08:50 -0800 skrev Luc Igert:
>> Hi Amos, and thanks a lot for your answer.I Forgot to say I’m
>> running as a
>> Reverse Proxy with multiple backends, Squid 3.1
>>
>> What’s  confusing for me is the fact that www.xxx.ch is working,
>> while
>> backup.xxx.ch or wbbltest.xxx.ch aren’t.
>
> So what cache_peer and cache_peer_access/cache_peer_domain rules do
> you
> have?

Three properly configured cache_peer, with unique cache_peer_domain and
a vhost port.


>> http_access allow manager localhost
>> http_access allow manager localnet
>> http_access allow localnet
>> http_access allow localhost
>> http_access allow manager
>> http_access deny !Safe_ports

This might be part of the problem. reverse-proxy traffic does not work
well behind forward-proxy security limitations.

...

>> http_port 80 accel defaultsite=backup.XXX.ch vhost

>> cache_peer 172.17.2.30 parent 80 0 no-query no-digest originserver
name=mysite1
>> cache_peer 172.17.2.32 parent 80 0 no-query no-digest originserver
name=mysite2
>> cache_peer 172.17.2.116 parent 80 0 no-query no-digest originserver
name=mysite3

>>
>> cache_peer_domain mysite1 www.XXX.ch
>> cache_peer_domain mysite2 wbbltest.XXX.ch
>> cache_peer_domain mysite3 backup.XXX.ch
>>
>> acl my_site1 dstdomain www.XXX.ch
>> acl my_site2 dstdomain wbbltest.XXX.ch
>> acl my_site3 dstdomain backup.XXX.ch
>> acl myaccelport port 80
>> acl myaccelport2 port 8080
>>
>> http_access allow my_site1 myaccelport
>> http_access allow my_site2 myaccelport
>> http_access allow my_site3 myaccelport2

This last rule might be the issue with backup.*. Expecting traffic on
port 80 to be received with port value 8080. To pass that ACL requires
the sending client to violate HTTP specifications, sending "Host:
backup.XXX.ch:8080" when the host authority is actually
"backup.XXX.ch:80"


It could also be a dead peer (or firewall) issue since wbbltest.* is
breaking too. Or broken origin server configuration.

Amos

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Unable to forward this request at this time.

Luc Igert
Thanks Amos, Thanks Henrik

Well my accelport2 was only a test..I changed the webserver back to port 80, replaced the last rule by http_access allow my_site3 myaccelport

About Security limitaions, what would be the right way to write it for reverse proxy then?

I tried telneting to port 80 on my 3 ips from the squid box, and It works fine.
I did see a connection Timeout on wbbltest.xxx (110) once as I tried accessing it. Now I have the same error again.

Any Idea?

Regards,
Luc.
12
Loading...