What is the Best Way to Set Up a Proxy Server to Connect to a Network Server Without Taking Down the Firewall?

Help
#1

This topic was automatically generated from Slack. You can find the original thread here.

However, we get a constant fail cause our firewall and sounds like we need a proxy server. I am super new to proxy servers and have no clue where to start and can’t afford teams plan for company atm. I basically want my workflow to run through PD to my Network Server but integrate a proxy server so I don’t have to bring down FW.

#2

For this, I think your Firewall might need to whitelist Pipedream’s IP range. Could you read through the article?

#3

We’ve attempted this for all ips listed to no luck.

#4

We keep getting a timeout fail.

#5

I’m not very sure about this case.

Hello , could you advice this case when you’re available?

#6 
[pipedream.com](http://pipedream.com)
**.[pipedream.com](http://pipedream.com)
**pipedream*.com
23.20.0.0/14
50.16.0.0/15
50.19.0.0/16
50.19.0.0/16
52.4.0.0/14
54.80.0.0/13
54.88.0.0/14
54.92.128.0/17
54.144.0.0/14
54.152.0.0/16
54.156.0.0/14
54.160.0.0/13
54.172.0.0/15
54.174.0.0/15
54.196.0.0/15
54.198.0.0/16
54.204.0.0/15
54.208.0.0/15
54.210.0.0/15
54.221.0.0/16
54.226.0.0/15
54.224.0.0/15
54.231.0.0/17
54.231.0.0/17
54.234.0.0/15
54.236.0.0/15
54.239.8.0/21
54.239.16.0/20
54.239.98.0/24
54.239.104.0/23
54.239.104.0/23
54.240.196.0/24
54.240.216.0/22
54.240.232.0/22
54.242.0.0/15
67.202.0.0/18
72.21.192.0/19
72.44.32.0/19
75.101.128.0/17
107.20.0.0/14
174.129.0.0/16
176.32.120.0/22
176.32.96.0/21
184.72.64.0/18
184.72.128.0/17
184.73.0.0/16
204.236.192.0/18
205.251.224.0/22
205.251.240.0/22
205.251.244.0/23
205.251.247.0/24
205.251.248.0/24
205.251.255.0/24
207.171.160.0/20
207.171.176.0/20
216.182.224.0/20
216.182.224.0/20
204.236.192.0/18
184.73.0.0/16
84.72.128.0/17
184.72.64.0/18
174.129.0.0/16
107.20.0.0/14
75.101.128.0/17
72.44.32.0/19
67.202.0.0/18
54.242.0.0/15
54.236.0.0/15
54.226.0.0/15
54.224.0.0/15
54.221.0.0/16
54.210.0.0/15
54.208.0.0/15
54.204.0.0/15
54.198.0.0/16
54.196.0.0/15
54.174.0.0/15
54.172.0.0/15
54.160.0.0/13
54.156.0.0/14
54.152.0.0/16
54.144.0.0/14
54.92.128.0/17
54.88.0.0/14
54.80.0.0/13
52.4.0.0/14
52.0.0.0/24
50.19.0.0/16
50.16.0.0/15
23.20.0.0/14
44.0.0.0/24
3.0.0.0/24
107.0.0.0/24
18.0.0.0/24
34.0.0.0/24
3.208.254.105
3.212.246.173
3.223.179.131
3.227.157.189
3.232.105.55
3.234.187.126
18.235.13.182
34.225.84.31
52.2.233.8
52.23.40.208
52.202.86.9
52.207.145.190
54.86.100.50
54.88.18.81
54.161.28.250
107.22.76.172

Here’s every IP whitelisted to our server.

#7
#8

Not sure if you can view that off your admin but basically we’re polling AT for form submissions, when submitted running an HTTP POST to our server for account creation.

#9

It seems to work when firewall is down

#10

but when up it fails due to timeout

#11

Hi Dominic,

We can provide an HTTP proxy for Teams customers, but if that’s not an option for you then you’ll have to deploy, configure and set up your own.

I suggest reading about the Squid proxy that’s installable on any VPS. Then you’ll need to configure it to allow a secure connection between Pipedream and your service.