I try to run my OpenVPN client on my windows 10 machine in order to connect to a remote OpenVPN CentOS 7 server but it does not work. I get the error below:
Options error: --capath fails with 'C:\Users\Desktop\OpenVPN\ca.crt': No such process (errno=3)
Options error: --cert fails with 'C:\Users\Desktop\OpenVPN\Win10client.crt': No such process (errno=3)
Fri Mar 22 22:56:20 2019 WARNING: cannot stat file 'C:\Users\Desktop\OpenVPN\Win10client.key': No such process (errno=3)
Options error: --key fails with 'C:\Users\Desktop\OpenVPN\Win10client.key'
Fri Mar 22 22:56:20 2019 WARNING: cannot stat file 'C:\Users\Desktop\OpenVPN\myvpn.tlsauth': No such process (errno=3)
Options error: --tls-crypt fails with 'C:\Users\Desktop\OpenVPN\myvpn.tlsauth': No such process (errno=3)
This is the config that I have on my ovpn file:
client
tls-client
--capath C:\\Users\\Desktop\\OpenVPN\\ca.crt
--cert C:\\Users\\Desktop\\OpenVPN\\Win10client.crt
--key C:\\Users\\Desktop\\OpenVPN\\Win10client.key
--tls-crypt C:\\Users\\Desktop\\OpenVPN\\myvpn.tlsauth
remote-cert-eku "TLS Web Client Authentication"
proto udp
remote serveraddress 1194 udp
dev tun
topology subnet
pull
Assuming your config file is well done. Try to reinstall openvpn, and put your config file to the c:/program files/openvpn/config folder. Then you can start the openvpn Service. Therefore you dont need to use the Openvpn gui.
Related
Hello i like to change to VSCodium with linux but i have a problem, in VSCODE i use remote-ssh and works fine, but this same package in VSCodium doesn't work.
It ask me password and after i have a error:
[20:38:29.280] SSH Resolver called for "ssh-remote+1.1.1.1", attempt 5, (Reconnection)
[20:38:29.281] SSH Resolver called for host: 1.1.1.1
[20:38:29.282] Setting up SSH remote "1.1.1.1"
[20:38:29.283] Acquiring local install lock: /var/folders/bz/gzbhhfv928n_jdqsk23ttycm0000gn/T/vscode-remote-ssh-eb13906b-install.lock
[20:38:29.283] Looking for existing server data file at /Users/XXXXXXXXXX/Library/Application Support/VSCodium/User/globalStorage/ms-vscode-remote.remote-ssh/vscode-ssh-host-eb13906b-cea9d1a4b17966719d8c5f3cdd914480f7cec47c-0.87.2022090715/data.json
[20:38:29.284] Using commit id "cea9d1a4b17966719d8c5f3cdd914480f7cec47c" and quality "stable" for server
[20:38:29.286] Install and start server if needed
[20:38:29.291] askpass server listening on /var/folders/bz/gzbhhfv928n_jdqsk23ttycm0000gn/T/vscode-ssh-askpass-da57138f4d7832fc3734ad7a50dc225ccbef89e5.sock
[20:38:29.291] Spawning local server with {"serverId":5,"ipcHandlePath":"/var/folders/bz/gzbhhfv928n_jdqsk23ttycm0000gn/T/vscode-ssh-askpass-de457e3bd9a608cfdd3faf37d5903491af5d4969.sock","sshCommand":"ssh","sshArgs":["-v","-T","-D","52249","-o","ConnectTimeout=15","1.1.1.1"],"serverDataFolderName":".vscodium-server","dataFilePath":"/Users/XXXXXXXXXX/Library/Application Support/VSCodium/User/globalStorage/ms-vscode-remote.remote-ssh/vscode-ssh-host-eb13906b-cea9d1a4b17966719d8c5f3cdd914480f7cec47c-0.87.2022090715/data.json"}
[20:38:29.291] Local server env: {"SSH_AUTH_SOCK":"/private/tmp/com.apple.launchd.DkNdtZMLnV/Listeners","SHELL":"/bin/zsh","DISPLAY":"1","ELECTRON_RUN_AS_NODE":"1","SSH_ASKPASS":"/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/local-server/askpass.sh","VSCODE_SSH_ASKPASS_NODE":"/Applications/VSCodium.app/Contents/Frameworks/VSCodium Helper.app/Contents/MacOS/VSCodium Helper","VSCODE_SSH_ASKPASS_EXTRA_ARGS":"--ms-enable-electron-run-as-node","VSCODE_SSH_ASKPASS_MAIN":"/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/askpass-main.js","VSCODE_SSH_ASKPASS_HANDLE":"/var/folders/bz/gzbhhfv928n_jdqsk23ttycm0000gn/T/vscode-ssh-askpass-da57138f4d7832fc3734ad7a50dc225ccbef89e5.sock"}
[20:38:29.292] Spawned 11544
[20:38:29.437] > local-server-5> Spawned ssh, pid=11548
[20:38:29.440] stderr> OpenSSH_8.6p1, LibreSSL 3.3.6
[20:38:29.490] stderr> ssh: connect to host 1.1.1.1 port 22: Connection refused
[20:38:29.492] > local-server-5> ssh child died, shutting down
[20:38:29.496] Local server exit: 0
[20:38:29.497] Received install output: local-server-5> Spawned ssh, pid=11548
OpenSSH_8.6p1, LibreSSL 3.3.6
ssh: connect to host 1.1.1.1 port 22: Connection refused
local-server-5> ssh child died, shutting down
[20:38:29.497] Failed to parse remote port from server output
[20:38:29.497] Resolver error: Error:
at g.Create (/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:583821)
at t.handleInstallOutput (/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:582473)
at Object.e [as tryInstallWithLocalServer] (/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:622972)
at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
at async /Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:642100
at async t.withShowDetailsEvent (/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:645820)
at async /Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:621444
at async T (/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:617950)
at async t.resolveWithLocalServer (/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:621059)
at async t.resolve (/Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:643428)
at async /Users/XXXXXXXXXX/.vscode-oss/extensions/ms-vscode-remote.remote-ssh-0.87.2022090715/out/extension.js:1:722225
[20:38:29.499] ------
Microsoft's remote extensions won't work with VSCodium because Microsoft restricted them to only work in VS Code. Their licenses also don't permit any usage in any editor other than Visual Studio family products. More context: https://news.ycombinator.com/item?id=31714082
I am using ubuntu 20.04 on wsl and installed postgres true the normal sudo apt-get install.
I know that there are related questions but none have solved my problem.
Whenever I run psql it returns me this error
psql: error: could not connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
I have tried to restart/start the psql server but then this error occured
$ sudo service postgresql start
* Starting PostgreSQL 13 database server * Error: /usr/lib/postgresql/13/bin/pg_ctl /usr/lib/postgresql/13/bin/pg_ctl start -D /var/lib/postgresql/13/main -l /var/log/postgresql/postgresql-13-main.log -s -o -c config_file="/etc/postgresql/13/main/postgresql.conf" exited with status 1:
2021-06-15 22:40:51.285 CEST [74] LOG: starting PostgreSQL 13.3 (Ubuntu 13.3-1.pgdg20.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, 64-bit
2021-06-15 22:40:51.297 CEST [74] LOG: could not bind IPv4 address "127.0.0.1": Permission denied
2021-06-15 22:40:51.297 CEST [74] HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2021-06-15 22:40:51.297 CEST [74] WARNING: could not create listen socket for "localhost"
2021-06-15 22:40:51.297 CEST [74] FATAL: could not create any TCP/IP sockets
2021-06-15 22:40:51.304 CEST [74] LOG: database system is shut down
pg_ctl: could not start server
Examine the log output.
I use google cloud shell to execute this program
Linux version
Distributor ID: Debian
Description: Debian GNU/Linux 10 (buster)
Release: 10
Codename: buster
Tor version 0.3.5.10.
When I tried restarting "sudo service tor restart" Tor I received an error
[ ok ] Stopping tor daemon...done (not running - there is no /run/tor/tor.pid).
[....] Starting tor daemon...Jun 27 01:51:04.132 [warn] Directory /var/lib/tor cannot be read: Permission denied
Jun 27 01:51:04.132 [warn] Failed to parse/validate config: Couldn't create private data directory "/var/lib/tor"
Jun 27 01:51:04.132 [err] Reading config failed--see warnings above.
failed.
So I set full permissions for the tor directory sudo chmod -R 777 /var/lib/tor
[FAIL] Checking if tor configuration is valid ... failed!
Jun 27 01:53:59.685 [notice] Tor 0.3.5.10 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1g, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.
Jun 27 01:53:59.685 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Jun 27 01:53:59.685 [notice] Read configuration file "/usr/share/tor/tor-service-defaults-torrc".
Jun 27 01:53:59.685 [notice] Read configuration file "/etc/tor/torrc".
Jun 27 01:53:59.688 [warn] Error setting groups to gid 114: "Operation not permitted".
Jun 27 01:53:59.688 [warn] If you set the "User" option, you must start Tor as root.
Jun 27 01:53:59.688 [warn] Failed to parse/validate config: Problem with User value. See logs for details.
Jun 27 01:53:59.688 [err] Reading config failed--see warnings above.
I use root privileges sudo su
[ ok ] Stopping tor daemon...done (not running - there is no /run/tor/tor.pid).
[....] Starting tor daemon...Jun 27 01:58:58.455 [warn] Directory /var/lib/tor cannot be read: Permission denied
Jun 27 01:58:58.455 [warn] Failed to parse/validate config: Couldn't create private data directory "/var/lib/tor"
Jun 27 01:58:58.455 [err] Reading config failed--see warnings above.
Is there any way that can help me solve my problem or how can i be able to install tor version 2.9.14?
You might have already solved the problem by now, if not I hope this can help.
Is there any way that can help me solve my problem?
OPTION 1
Let's take a look at these warnings:
[warn] Error setting groups to gid 114: "Operation not permitted".
[warn] If you set the "User" option, you must start Tor as root.
[warn] Failed to parse/validate config: Problem with User value.
To get a log of all users run cat /etc/passwd and you'll see debian-tor listed:
...
debian-tor:x:108:114::/var/lib/tor:/bin/false
...
The folder /var/lib/tor is owned by user debian-tor, so sudo -u debian-tor tor will work.
Alternatively, you can run this for your current user: (or chmod 777 for all)
chmod 700 -R /var/lib/tor/*
chown -R tor /var/lib/tor/
sudo service tor restart
You actually should run tor as non-root, else you get this message:
You are running Tor as root. You don't need to, and you probably shouldn't.
OPTION 2
As the warning suggests to see logs for details you should check for a message within dsmeg and /var/log/syslog. If you find anything then it can be AppArmor or SELinux blocking tor. Both SELinux and AppArmor provide a set of tools to isolate applications from each other to protect the host system from being compromised, so it's not recommended disabling them permanently but temporarily for debugging.
According to Debian SELinux support:
The Debian packaged Linux kernels have SELinux support compiled in,
but disabled by default.
Check the SELinux state with getenforce, if the output is Permissive or Disabled then you're set.
Moreover, looking at AppArmor/Progress:
Since Debian 10 (Buster), AppArmor is enabled by default.
To disable AppArmor on your system run: (reference)
sudo mkdir -p /etc/default/grub.d
echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=0"' \
| sudo tee /etc/default/grub.d/apparmor.cfg
sudo update-grub
sudo reboot
There's a chance that either one's the culprit. Users have reported similar issue here.
How can i be able to install tor version 2.9.14?
Downgrading the tor package is as simple as this:
sudo apt-get install tor=0.2.9.14
But why would you want do that?
tor v2 will be deprecated soon. You'll see warnings like:
[warn] At least one protocol listed as required in the consensus is
not supported by this version of Tor. You should upgrade. This version
of Tor will not work as a client on the Tor network. The missing
protocols are: DirCache=2 HSDir=2 HSIntro=4 Link=4-5
NB: Post on tor.stackexchange for tor related issues.
I upgraded my Linux kernel and dovecot failed to start with the following error messages:
Error: service(managesieve-login): listen(*, 4190) failed: Address already in use
Error: service(pop3-login): listen(*, 110) failed: Address already in use
Error: service(pop3-login): listen(*, 995) failed: Address already in use
Error: service(imap-login): listen(*, 143) failed: Address already in use
Error: service(imap-login): listen(*, 993) failed: Address already in use
Fatal: Failed to start listeners
Strangely enough, I couldn't find any process bounded to those port numbers. All commands below return nothing.
# netstat -tulpn | grep 110
# ss -tulpn |grep 110
# fuser 110/tcp
# lsof -i :110
I also tried to change the listen setting to my specific IP address and it still failed the same way.
Any idea how I can solve this problem? Here's my version info:
# uname -a
Linux ip-172-31-26-222 4.14.177-107.254.amzn1.x86_64 #1 SMP Thu May 7 18:30:14 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
# dovecot --version
2.2.36 (1f10bfa63)
Hi it looks like you are using AWS as I am. I recently updated via Yum as well. I noticed that a new package named 'portreserve' was also installed. I killed that process, left the /etc/dovecot/dovecot.conf as it was before and then started Dovecot successfully. I was also immediately able to reconnect my mail clients connection. I hope that helps you.
I also restarted the portreserve program since it seems useful to limit port access.
I can able to connect postgres from terminal as well as python manage.py dbshell command
But when i'm trying to connect from apache i'm Getting error as follows.
Error : OperationalError: could not connect to server: Permission denied
Is the server running on host "192.168.1.10" and accepting
TCP/IP connections on port 5432?
My listen Address on postgress conf file is 192.168.1.10 Address
pg_hg_cong allowed host all all 192.168.0.0/24 trust
And also selinux turned httpd_can_network_connect_db on
Port is listening on 192.168.1.10:5432 on netstat output.
And database's are storing in /tmp directory
wxrwxrwx. 1 postgres postgres 0 Dec 18 07:40 .s.PGSQL.5432
-rw-------. 1 postgres postgres 50 Dec 18 07:40 .s.PGSQL.5432.lock
Actually I have enabled selinux httpd_can_network_connect_db parameters on db server instead of web server
So issue got solved after enabling httpd_can_network_connect_db on web server