Issues connecting from the Pgadmin4 QueryTool over a VPN connection
I upgraded from pgadmin III to pgadmin4. I have installed it on a Windows 10 environment and I use a chrome browser.
Sometimes I work remotely (over OpenVPN), previously with pgadmin III without problems.
Now I have a problem. Pgadmin4 is connecting (locally and remotely over VPN) OK to servers and databases, but, the QueryTool is not connecting (the problem happens only when trying to access over VPN, locally it connects). After starting the QueryToll, the connection symbol (upper left) is not marking a successful connection.
I guess this could be related to the route the QueryTool is taking in order to access the DB server or perhaps a timeout (my connection can be slow)? The Pgadmin4 interface in the browser connects without issues, only the QueryTool fails to do so. Any hints or ideas to solve or overcome this?
Thanks!
See also questions close to this topic
-
Route instances of CMD through different VPN connections
I want to route various instances of cmd through different vpn connections, so each instance of cmd should go through a separate vpn connection. I am using OpenVPN as a vpn.
-
Why android phone connection openvpn often dropped?
I use the https://github.com/Nyr/openvpn-install for configure my openvpn.
My window computer can't connect, but the phone can.
My Android phone connection is often dropped.
How can I fix this problem? Thank you very much.
Here is the log when my phone openvpn is disconnected.
Jun 23 08:41:33 vps77304135 systemd[1]: Started OpenVPN service. Jun 23 08:42:05 vps77304135 openvpn[1083]: 120.236.146.39:33803 TLS: Initial packet from [AF_INET]120.236.146.39:33803, sid=6232cfee 89a097f7 Jun 23 08:42:09 vps77304135 openvpn[1083]: 120.236.146.39:33803 VERIFY OK: depth=1, CN=ChangeMe Jun 23 08:42:09 vps77304135 openvpn[1083]: 120.236.146.39:33803 VERIFY OK: depth=0, CN=qimi Jun 23 08:42:09 vps77304135 openvpn[1083]: 120.236.146.39:33803 peer info: IV_GUI_VER=OC30Android Jun 23 08:42:09 vps77304135 openvpn[1083]: 120.236.146.39:33803 peer info: IV_VER=3.2 Jun 23 08:42:09 vps77304135 openvpn[1083]: 120.236.146.39:33803 peer info: IV_PLAT=android Jun 23 08:42:09 vps77304135 openvpn[1083]: 120.236.146.39:33803 peer info: IV_NCP=2 Jun 23 08:42:09 vps77304135 openvpn[1083]: 120.236.146.39:33803 peer info: IV_TCPNL=1 Jun 23 08:42:09 vps77304135 openvpn[1083]: 120.236.146.39:33803 peer info: IV_PROTO=2 Jun 23 08:42:09 vps77304135 openvpn[1083]: 120.236.146.39:33803 peer info: IV_IPv6=0 Jun 23 08:42:09 vps77304135 openvpn[1083]: 120.236.146.39:33803 peer info: IV_AUTO_SESS=1 Jun 23 08:42:09 vps77304135 openvpn[1083]: 120.236.146.39:33803 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA Jun 23 08:42:09 vps77304135 openvpn[1083]: 120.236.146.39:33803 [qimi] Peer Connection Initiated with [AF_INET]120.236.146.39:33803 Jun 23 08:42:09 vps77304135 openvpn[1083]: MULTI: new connection by client 'qimi' will cause previous active sessions by this client to be dropped. Remember to use the --duplicate-cn option if you want multiple clients using the same certificate or username to concurrently connect. Jun 23 08:42:09 vps77304135 openvpn[1083]: MULTI_sva: pool returned IPv4=10.8.0.2, IPv6=(Not enabled) Jun 23 08:42:09 vps77304135 openvpn[1083]: MULTI: Learn: 10.8.0.2 -> qimi/120.236.146.39:33803 Jun 23 08:42:09 vps77304135 openvpn[1083]: MULTI: primary virtual IP for qimi/120.236.146.39:33803: 10.8.0.2 Jun 23 08:42:09 vps77304135 openvpn[1083]: qimi/120.236.146.39:33803 PUSH: Received control message: 'PUSH_REQUEST' Jun 23 08:42:09 vps77304135 openvpn[1083]: qimi/120.236.146.39:33803 SENT CONTROL [qimi]: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route-gateway 10.8.0.1,topology subnet,ping 10,ping-restart 120,ifconfig 10.8.0.2 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1) Jun 23 08:42:09 vps77304135 openvpn[1083]: qimi/120.236.146.39:33803 Data Channel: using negotiated cipher 'AES-256-GCM' Jun 23 08:42:09 vps77304135 openvpn[1083]: qimi/120.236.146.39:33803 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Jun 23 08:42:09 vps77304135 openvpn[1083]: qimi/120.236.146.39:33803 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Jun 23 08:44:07 vps77304135 openvpn[1083]: 112.74.179.83:6809 TLS: Initial packet from [AF_INET]112.74.179.83:6809, sid=4c0f204b 75afb48c Jun 23 08:44:13 vps77304135 openvpn[1083]: 112.74.179.83:6809 VERIFY OK: depth=1, CN=ChangeMe Jun 23 08:44:13 vps77304135 openvpn[1083]: 112.74.179.83:6809 VERIFY OK: depth=0, CN=qimi Jun 23 08:44:14 vps77304135 openvpn[1083]: 112.74.179.83:6809 peer info: IV_VER=2.4.7 Jun 23 08:44:14 vps77304135 openvpn[1083]: 112.74.179.83:6809 peer info: IV_PLAT=linux Jun 23 08:44:14 vps77304135 openvpn[1083]: 112.74.179.83:6809 peer info: IV_PROTO=2 Jun 23 08:44:14 vps77304135 openvpn[1083]: 112.74.179.83:6809 peer info: IV_NCP=2 Jun 23 08:44:14 vps77304135 openvpn[1083]: 112.74.179.83:6809 peer info: IV_LZ4=1 Jun 23 08:44:14 vps77304135 openvpn[1083]: 112.74.179.83:6809 peer info: IV_LZ4v2=1 Jun 23 08:44:14 vps77304135 openvpn[1083]: 112.74.179.83:6809 peer info: IV_LZO=1 Jun 23 08:44:14 vps77304135 openvpn[1083]: 112.74.179.83:6809 peer info: IV_COMP_STUB=1 Jun 23 08:44:14 vps77304135 openvpn[1083]: 112.74.179.83:6809 peer info: IV_COMP_STUBv2=1 Jun 23 08:44:14 vps77304135 openvpn[1083]: 112.74.179.83:6809 peer info: IV_TCPNL=1 Jun 23 08:44:21 vps77304135 openvpn[1083]: 112.74.179.83:6809 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA Jun 23 08:44:21 vps77304135 openvpn[1083]: 112.74.179.83:6809 [qimi] Peer Connection Initiated with [AF_INET]112.74.179.83:6809 Jun 23 08:44:21 vps77304135 openvpn[1083]: MULTI: new connection by client 'qimi' will cause previous active sessions by this client to be dropped. Remember to use the --duplicate-cn option if you want multiple clients using the same certificate or username to concurrently connect. Jun 23 08:44:21 vps77304135 openvpn[1083]: MULTI_sva: pool returned IPv4=10.8.0.2, IPv6=(Not enabled) Jun 23 08:44:21 vps77304135 openvpn[1083]: MULTI: Learn: 10.8.0.2 -> qimi/112.74.179.83:6809 Jun 23 08:44:21 vps77304135 openvpn[1083]: MULTI: primary virtual IP for qimi/112.74.179.83:6809: 10.8.0.2 Jun 23 08:44:22 vps77304135 openvpn[1083]: qimi/112.74.179.83:6809 PUSH: Received control message: 'PUSH_REQUEST' Jun 23 08:44:22 vps77304135 openvpn[1083]: qimi/112.74.179.83:6809 SENT CONTROL [qimi]: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 8.8.8.8,dhcp-option DNS 8.8.4.4,route-gateway 10.8.0.1,topology subnet,ping 10,ping-restart 120,ifconfig 10.8.0.2 255.255.255.0,peer-id 1,cipher AES-256-GCM' (status=1) Jun 23 08:44:22 vps77304135 openvpn[1083]: qimi/112.74.179.83:6809 Data Channel: using negotiated cipher 'AES-256-GCM' Jun 23 08:44:22 vps77304135 openvpn[1083]: qimi/112.74.179.83:6809 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Jun 23 08:44:22 vps77304135 openvpn[1083]: qimi/112.74.179.83:6809 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Jun 23 08:44:27 vps77304135 openvpn[1083]: qimi/112.74.179.83:6809 PUSH: Received control message: 'PUSH_REQUEST' -
Create rules to access website only via openvpn
I have VPS with HTTPD and OpenVPN in docker. OpenVPN is working fine. What I need is to make website on the VPS accessible only using VPN. I suppose I can do that using iptables but dont know how exactly.
I have IPv4 forwarding enabled.
The problem is that I have no idea if iptables is the place where I need to do the change for this to work.
OpenVPN configuration:
server 192.168.255.0 255.255.255.0 verb 3 key /etc/openvpn/pki/private/*******.key ca /etc/openvpn/pki/ca.crt cert /etc/openvpn/pki/issued/*******.crt dh /etc/openvpn/pki/dh.pem tls-auth /etc/openvpn/pki/ta.key key-direction 0 keepalive 10 60 persist-key persist-tun proto udp # Rely on Docker to do port mapping, internally always 1194 port 1194 dev tun0 status /tmp/openvpn-status.log user nobody group nogroup client-to-client comp-lzo no ### Route Configurations Below #route 192.168.254.0 255.255.255.0 route 192.168.255.0 255.255.255.0 ### Push Configurations Below push "block-outside-dns" push "dhcp-option DNS 8.8.8.8" push "dhcp-option DNS 8.8.4.4" push "comp-lzo no" push "redirect-gateway def1"IPTABLES:
iptables -t nat -S -P PREROUTING ACCEPT -P INPUT ACCEPT -P OUTPUT ACCEPT -P POSTROUTING ACCEPT -N DOCKER -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER -A OUTPUT ! -d 127.0.0.0/8 -m addrtype --dst-type LOCAL -j DOCKER -A POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE -A POSTROUTING -s 192.168.255.0/24 -o eth0 -j MASQUERADE -A POSTROUTING -o eth0 -j MASQUERADE -A DOCKER -i docker0 -j RETURN iptables -S -P INPUT ACCEPT -P FORWARD DROP -P OUTPUT ACCEPT -N DOCKER -N DOCKER-ISOLATION-STAGE-1 -N DOCKER-ISOLATION-STAGE-2 -N DOCKER-USER -N f2b-postfix -N f2b-sshd -A INPUT -p tcp -m multiport --dports 22 -j f2b-sshd -A INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -j DROP -A INPUT -p tcp -m tcp ! --tcp-flags FIN,SYN,RST,ACK SYN -m state --state NEW -j DROP -A INPUT -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN,RST,PSH,ACK,URG -j DROP -A INPUT -i lo -j ACCEPT -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT -A INPUT -s 123.183.209.136/32 -j DROP -A INPUT -i eth0 -p udp -m state --state NEW -m udp --dport 1194 -j ACCEPT -A INPUT -i tun0 -j ACCEPT -A INPUT -s 192.168.255.0/24 -i tun0 -j ACCEPT -A FORWARD -j DOCKER-USER -A FORWARD -j DOCKER-ISOLATION-STAGE-1 -A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A FORWARD -o docker0 -j DOCKER -A FORWARD -i docker0 ! -o docker0 -j ACCEPT -A FORWARD -i docker0 -o docker0 -j ACCEPT -A FORWARD -i tun0 -o eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -i eth0 -o tun0 -m state --state RELATED,ESTABLISHED -j ACCEPT -A FORWARD -i tun0 -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT -A OUTPUT -d 192.168.255.0/24 -o tun0 -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT -A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2 -A DOCKER-ISOLATION-STAGE-1 -j RETURN -A DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP -A DOCKER-ISOLATION-STAGE-2 -j RETURN -A DOCKER-USER -j RETURNip route: dev eth0 10.20.100.0/24 dev eth0 proto kernel scope link src 10.20.100.200 169.254.0.0/16 dev eth0 scope link metric 1002 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 192.168.255.0/24 via 192.168.255.2 dev tun0 192.168.255.2 dev tun0 proto kernel scope link src 192.168.255.1
Here I have changed the public IP to 10.20.100.200
I expect to be able to access the website only when the client is connected via vpn. I have made htaccess whicch allows only IP range:
order deny,allow deny from all allow from 192.168.255.0/24
But now webserver gives me error 403 and in accesslog I see: [Fri Jun 21 08:15:35.106343 2019] [access_compat:error] [pid 3764] [client 89.24.61.242:23826] AH01797: client denied by server configuration
IP 89.24.61.242 is public IP of my mobile data provider. This is happening even though I am connected to VPN.
-
Query editor not connection to database
I'm using PG_Admin 4.8 on Windows 10
The Query editor doesn't connect to the database.
I looked at the posting: pgAdmin 4 Query Tool not connecting to database
I can't make a query using psql
Without solving the connection problem, I did the following steps: I deleted the Server in PG_Admin, stopped and re-started the postgresql-x64-11 service and re-created the server in PG_Admin. I deleted the database and restored it from backup.
-
pgadmin4 not displaying properly
I've installed PostgreSql, pgadmin4 came along with it first. It didn't work so I installed the latest version of pgadmin4 v4 again but still its the same. It was showing a fatal error message earlier which said "Failed to open the system default web browser. Is one installed?." After that, it somehow worked & it started in my IE when I set it as my default browser. I tried opening it in Firefox too setting it as default browser but the result was same.
It shows the following screen rather than the expected normal screen that should appear as soon as we start it.
-
Changing Dashboard Settings From Configuration File: PG Admin4
I am trying to find a way to easily deploy a change to everybody in my large group using PG Admin 4.
Our goal is to reduce performance issues that can be caused by a few of the dashboard settings.
I need to find the necessary file to change the value of: show activity, show graph data points, show graphs and show mouse hover tooltip, to false.
I have already looked through the documentation and cannot seem to find how to do this clearly stated anywhere.
Any help/guidance would be appreciated.
Thanks in advance!
Changing the values in initpy
The changed values are not reflected in the web browser.