I have set up a squid proxy on a Ubuntu machine, and I'd like to do some testing by accessing the proxy from another computer (NOT on the same lan). But I seem to be unable to connect to the squid proxy server.
I've tried several different ways to connect: by setting the proxy in my web browser, and by using the unix program "curl" to issue http requests from a command line. But I just can't connect.
I've tried setting the acl in the configuration file squid.conf to allow access from the remote machine. So I don't know what's going on. If I try to access the internet from the same machine that the squid proxy is on, it works correctly.
The lines in squid.conf that I added to allow access from the remote machine are:
acl my_machine src 50.193.61.125/255.255.255.0
http_access allow my_machine
Is there anything else that needs to be done to allow the remote machine to access the squid proxy?
Thanks.
got the same problem. ec2 instance with fedora 19 os and squid 3.2.9. also created a security group incoming rule for port 3128. wont work if i connect from a remote pc. think there is a restriction in the aws-cloud.
Related
I have Xampp on a server and am able to access it from inside my local network, I have 3 vpns to other rooftops that can ping the server just fine, but can't get xampp to allow them to pull up a web page on the server outside the local network.
found this on the web, works for local but not the vpns:
Allow from ::1 127.0.0.0/8 x.x.x.0/8\
fc00::/7 10.0.0.0/8 172.16.0.0/12 x.x.0.0/16\
fe80::/10 169.254.0.0/16
how do you allow access to a webpage through your vpns and not screw up security with 'Allow from all'?
If you dont want to whitelist all connections you will have to set up 3 rules.
If it works for the local network it should work for VPNs either. So i guess you have a problem by detecting the correct ips for the vpns.
They depend on which kind of VPN you are using:
If it is a End-to-End VPN you should know the VPN Net ip and subnet mask. You can look for it in the vpn adapters settings.
If it is a Site-to-End VPN there should be no problem as the clients are a part of the local network.
If it is a site-to-site VPN and there are no forwarding rules active you also wouldnt have a problem. Unless the ip addresses overlap.
If you are working with forwarding it will be very hard to handle the different ip ranges. So consider using a simple vpn.
I hope i got your question right and it may help someone:)
I want to have a SSH connection from my local windows machine or VM on my computer to Azure windows server VM. I tried Cygwin and Putty but both of them gave timeout connection. I used public ip address and opened port 22 on Azure VM.
I will appreciate if some one can give me any hints or links.
There are multiple firewalls that can be the reason here. Fist you must have a rule on the server to allow incoming SSH requests (port 22). Then you need to configure the NSG(Network security group) to allow incoming on port 22. If it still doesn't work, you need to verify that you are allowed to do an outgoing SSH request from your computer.
Thanks for suggestions, I found the problem which was the host machine IP address(ipconfig) (where is a local VM inside domain) was different from the IP address that communicate outside the domain to internet. I was set in NSG of Azure VM to only accept this IP and because of that it gave time-out error. After changing the IP it works.
I have a VPN (pptpd) server configured and a client connected. In the same machine of VPN server, I have a proxy server (port 3128)(squid) running with authentication enabled. When I use the proxy in my firefox browser it works fine. However, when I conect my notebook to my VPN server I can't navigate using firefox + proxy. Just to remember Proxy server and VPN server running in same machine (a VPS). I'm using UFW firewall.
Is there some tips in configuration files (pptpd or squid) to get this problem fixed?
Best Regards!
use squid's access.log to make sure: squid doesn't receive requests from your notebook; check the routing availability between internal IP network of VPN server and proxy address, it must be accessible (pingable). you may use port address translation (PAT) as a simple fix.
I am using Neo4j graph database. Its running on Windows PC at url: http://localhost:7474/browser/. Now I want to get access to this server from machine running Ubuntu OS, so that I can access Neo4j browser and can use it for development purpose as well.
Here is what you need to do: -
Uncomment "org.neo4j.server.webserver.address" and provide a valid IP-Address on which you want to bind your neo4j http service at port 7474 in your neo4j-server.properties and restart your neo4j server.
Try accessing you Neo4j server on local machine by entering URL - http://:7474/ (Do not use localhost).
Switch off all firewalls and ensure :7474 is accessible from any remote machine. You may test it with Telnet too.
In case all the above works then you are done and your Neo4j server is accessible from remote machine.
I think you'll need to configure your conf/neo4j-server.properties file to allow access from non-localhost addresses. Here's the relevant part of my file:
# Let the webserver only listen on the specified IP. Default is localhost (only
# accept local connections). Uncomment to allow any connection. Please see the
# security section in the neo4j manual before modifying this.
#org.neo4j.server.webserver.address=0.0.0.0
I have set up a FTP server with Apache FTP server on local machine, this machine can access internet but its IP address cannot be accessed externally.
I also have another machine in a different city - it can access the internet but it is same in that its IP address cannot be accessed externally. The two computers are not on the same network so they are unable ping each other.
How I can use FTP client from another machine to access the FTP server, I know it should be impossible but do you guys have any workarounds (whatever code change or other approaches)
I am in the US - do you guys have idea how I can make my home IP publicly accessible?
it is very possible if you control the firewall that the server is behind. this is standard network configuration, and you can find hundreds of tutorials online, but the most important bit of information is the firewall, not the ftp server. you configure port forwarding on your firewall to forward incoming ftp requests to your internal ftp server. also, you will want to use "passive" ftp from the client because the client is also behind a firewall.