Forwarding Error 1007

Discuss and get help configuring CacheGuard to protect Web servers
Post Reply
GEROholding
Posts: 5
Joined: 06 Jun 2018 07:05

Forwarding Error 1007

Post by GEROholding » 06 Jun 2018 08:41

Hi Folks,

Unfortunately I’m experiencing problems with CacheGuard in rweb mode. When I’m accessing our HTTP Webserver through the CacheGuard Appliance from our internal network, it’s working fine. But when I’m trying to access via Internet (Internet > Firewall > CacheGuard > Webserver) I get “Error 1007 – forwarding not available”.

In the Firewall I’ve forwarded port 80 to the CacheGuard Appliance. There is no packet drop in the firewall. Wireshark says that the CacheGuard Appliance returns Error 500 to the client. I can see the Error 500 only in Wireshark.

(I’ve also tried it with SSL offloading. In this Case the SSL handshake works fine, but after the successful encryption I get the Error 1007 page)

This is, when I’m using no waf. When I activate waf, I get the error “no access right to the directory”.


Thank you in advance!

User avatar
david
Posts: 157
Joined: 08 Aug 2015 20:38

Re: Forwarding Error 1007

Post by david » 06 Jun 2018 10:12

Hi,

Thank you for your post.

The error 1007 means that CG is unable to properly reach backend web servers. Not because there is a TCP connectivity issue (Error 1009) but because backend web servers can't properly handle requests coming from CG. Quite frequently, this is due to virtual hosts misconfiguration on backend Web server.

Can you please have a look on your Web server configuration and verify that all virtual hosts are properly defined? I would also be interested in getting the output of the following commands:

Code: Select all

rweb site
rweb host
Best Regards,
David Jan
CacheGuard Technical Team
https://www.cacheguard.com

GEROholding
Posts: 5
Joined: 06 Jun 2018 07:05

Re: Forwarding Error 1007

Post by GEROholding » 08 Jun 2018 07:39

Hi David,
I've already found the problem. It was a misconfiguration in the A-Record of my Domain. CacheGuard didn't know the specified domain in the A-Record, in other words the http request contained a wrong domain, and so CG blocked access from outsite the external network (internet).
It's my first try with a reverse proxy. But I really appreciate CacheGuard. It's simple and easy to use.
Thank you very much.

User avatar
david
Posts: 157
Joined: 08 Aug 2015 20:38

Re: Forwarding Error 1007

Post by david » 08 Jun 2018 10:03

Hi,

Oh I see. I think that you talk about an A record in your local DNS server which should associate the name to CG's external IP address (a private IP address). In any case, I'm happy to hear that you resolved the issue.

Best Regards,
David Jan
CacheGuard Technical Team
https://www.cacheguard.com

Post Reply