我有启用了 VPN 的 VPS Windows 服务器。
我已经用安卓手机和windows10连接到那个VPN。
但我想用 Ubuntu 20.04 连接到它并得到“连接失败”。
新的 Ubuntu 有问题吗？我应该更改连接配置吗？
我已通过其他平台连接到该 VPN，但无法连接到 Ubuntu。
当我使用调试后缀 ( nemo --debug)启动 Nemo 并且未启动和连接MEGASync时，我在命令行上收到错误消息：
** (nemo:70308): WARNING **: 14:01:02.206: connect() failed
并且：
** (nemo:70308): WARNING **: 14:21:07.205: connect() failed
** (nemo:70308): DEBUG: 14:21:07.221: mega_ext_get_file_items: 0
** (nemo:70308): DEBUG: 14:21:07.474: mega_ext_get_file_items: 0
** (nemo:70308): DEBUG: 14:21:07.681: mega_ext_get_file_items: 0
** (nemo:70308): DEBUG: 14:21:07.908: mega_ext_get_file_items: 0
** (nemo:70308): DEBUG: 14:21:08.158: mega_ext_get_file_items: 0
当我启动 MEGASync 时，警告消失。由于我的 Ubuntu 20.04 上出现 Nemo 随机崩溃，我想知道是否存在连接以及如何停止这些警告。我没有在 MEGASync 的首选项中找到停止 MEGASync Nemo 扩展要求每秒检查连接的选项。可能这个警告是良性的，我就离开了。
任何提示或帮助？
我在 Ubuntu 20.04 上运行 OpenVPN。我在两个不同的欧洲国家/地区的办公室有两个 VPN。我发现可以同时连接两者。就连通性而言，这将如何运作？应用程序如何“选择”要使用的连接以及同时打开两者是否有益？或者也许只是看起来它们都是打开的，最新的连接“覆盖”了前一个连接？
我目前正在运行 Kubuntu 20.04 并尝试连接新的耳塞（Sennheiser Momentum 真无线 2），但我连接了耳塞，一秒钟后断开连接，然后它尝试再次连接，依此类推。我尝试连接其他耳塞（Samsung Gear IconX2018），它可以正常工作。PC上的蓝牙加密狗和笔记本电脑的蓝牙也是如此。还从 USB 棒上运行了 Win7 便携版，它找到了来自 MS 的驱动程序并且连接正常。
bluetootsctl 输出：
Agent registered
[CHG] Controller 00:1A:7D:DA:71:09 Discovering: yes
[NEW] Device 00:1B:66:BC:2E:F9 MOMENTUM TW 2
[CHG] Device 00:1B:66:BC:2E:F9 RSSI: -66
[CHG] Device 00:1B:66:BC:2E:F9 TxPower: -12
[CHG] Device 00:1B:66:BC:2E:F9 UUIDs: 0000180a-0000-1000-8000-00805f9b34fb
[CHG] Device 00:1B:66:BC:2E:F9 UUIDs: 0000180f-0000-1000-8000-00805f9b34fb
[CHG] Device 00:1B:66:BC:2E:F9 UUIDs: 0000fdce-0000-1000-8000-00805f9b34fb
[NEW] Device B0:FA:EB:2F:9E:3D B0FAEB2F9E3C
[NEW] Device D0:20:92:CF:BE:8B fenix 3
[CHG] Device 00:1B:66:BC:2E:F9 RSSI: -93
[CHG] Device 00:1B:66:BC:2E:F9 RSSI: -59
[NEW] Device F4:7D:EF:FF:9E:87 Galaxy Fitⓔ (9E87)
[CHG] Controller 00:1A:7D:DA:71:09 Discovering: no
[CHG] Device F4:7D:EF:FF:9E:87 RSSI is nil
[CHG] Device D0:20:92:CF:BE:8B RSSI is nil
[CHG] Device B0:FA:EB:2F:9E:3D RSSI is nil
[CHG] Device 00:1B:66:BC:2E:F9 TxPower is nil
[CHG] Device 00:1B:66:BC:2E:F9 RSSI is nil
[CHG] Device 00:1B:66:BC:2E:F9 Connected: yes
[CHG] Device 00:1B:66:BC:2E:F9 Modalias: usb:v1377p7001d0480
[CHG] Device 00:1B:66:BC:2E:F9 UUIDs: 00001101-0000-1000-8000-00805f9b34fb
[CHG] Device 00:1B:66:BC:2E:F9 UUIDs: 00001108-0000-1000-8000-00805f9b34fb
[CHG] Device 00:1B:66:BC:2E:F9 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device 00:1B:66:BC:2E:F9 UUIDs: 0000110b-0000-1000-8000-00805f9b34fb
[CHG] Device 00:1B:66:BC:2E:F9 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device 00:1B:66:BC:2E:F9 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:1B:66:BC:2E:F9 UUIDs: 0000111e-0000-1000-8000-00805f9b34fb
[CHG] Device 00:1B:66:BC:2E:F9 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device 00:1B:66:BC:2E:F9 UUIDs: 0000eb03-d102-11e1-9b23-00025b00a5a5
[CHG] Device 00:1B:66:BC:2E:F9 ServicesResolved: yes
[CHG] Device 00:1B:66:BC:2E:F9 Paired: yes
[CHG] Device 00:1B:66:BC:2E:F9 Trusted: yes
[CHG] Device 00:1B:66:BC:2E:F9 ServicesResolved: no
[CHG] Device 00:1B:66:BC:2E:F9 Connected: no
[CHG] Device 00:1B:66:BC:2E:F9 Connected: yes
[CHG] Device 00:1B:66:BC:2E:F9 Connected: no
[CHG] Device 00:1B:66:BC:2E:F9 Connected: yes
[CHG] Device 00:1B:66:BC:2E:F9 Connected: no
lspci -knn | grep 网络 -A3; lsusb：
Bus 002 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 005: ID 046d:0843 Logitech, Inc. Webcam C930e
Bus 002 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 002 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 002: ID 046d:c333 Logitech, Inc. Gaming Keyboard G610
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 0bda:5411 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 003: ID 0bda:0411 Realtek Semiconductor Corp.
Bus 010 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
journalctl -u 蓝牙 | 尾巴：
bluetoothd[965]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/A2DPSource/sbc
bluetoothd[965]: /org/bluez/hci0/dev_88_BD_45_D1_39_35/sep2/fd0: fd(58) ready
bluetoothd[965]: a2dp-source profile connect failed for 00:1B:66:BC:2E:F9: Device or resource busy
bluetoothd[965]: No reply to Start request
bluetoothd[965]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
bluetoothd[965]: No reply to Start request
bluetoothd[965]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
bluetoothd[965]: connect error: Connection refused (111)
bluetoothd[965]: connect error: Connection refused (111)
bluetoothd[965]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
bluetoothd[965]: No reply to Start request
bluetoothd[965]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
bluetoothd[965]: No reply to Start request
bluetoothd[965]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
bluetoothd[965]: No reply to Start request
bluetoothd[965]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
bluetoothd[965]: No reply to Start request
bluetoothd[965]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
systemctl 状态蓝牙：
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2020-07-06 20:25:17 CEST; 15h ago
Docs: man:bluetoothd(8)
Main PID: 965 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 14263)
Memory: 3.5M
CGroup: /system.slice/bluetooth.service
└─965 /usr/lib/bluetooth/bluetoothd
bluetoothd[965]: connect error: Connection refused (111)
bluetoothd[965]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
bluetoothd[965]: No reply to Start request
bluetoothd[965]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
bluetoothd[965]: No reply to Start request
bluetoothd[965]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
bluetoothd[965]: No reply to Start request
bluetoothd[965]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
bluetoothd[965]: No reply to Start request
bluetoothd[965]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
dpkg -l | grep 蓝色
ii bluedevil 4:5.18.4.1-0ubuntu1 amd64 KDE Bluetooth stack
ii bluez 5.53-0ubuntu3 amd64 Bluetooth tools and daemons
ii bluez-cups 5.53-0ubuntu3 amd64 Bluetooth printer driver for CUPS
ii bluez-obexd 5.53-0ubuntu3 amd64 bluez obex daemon
ii libbluetooth3:amd64 5.53-0ubuntu3 amd64 Library to use the BlueZ Linux Bluetooth stack
ii libkf5bluezqt-data 5.68.0-0ubuntu1 all data files for bluez-qt
ii libkf5bluezqt6:amd64 5.68.0-0ubuntu1 amd64 Qt wrapper for bluez
ii pulseaudio-module-bluetooth 1:13.99.1-1ubuntu3.3 amd64 Bluetooth module for PulseAudio sound server
ii qml-module-org-kde-bluezqt:amd64 5.68.0-0ubuntu1 amd64 QML wrapper for bluez
任何帮助和提示都非常感谢。如果需要一些额外的信息，请告诉。
当我启动计算机时，一切正常，但从挂起应用程序恢复后，无法打开新的本地套接字。我的连接和 DNS 都很好。我可以ping 域。我可以浏览网站，我可以通过 SSH 连接，我可以连接到在恢复之前启动的服务。但我无法启动任何想要绑定到新本地套接字的东西。如果我重新启动一切都会再次工作，但我必须强制重新启动，因为停止 Tomcat 会停止等待网络。
亚行：
adb F 05-03 15:31:03 54241 54241 main.cpp:148] could not install *smartsocket* listener: Address family not supported by protocol
* failed to start daemon
adb: failed to check server version: cannot connect to daemon
雄猫：
java.net.BindException: Cannot assign requested address (Bind failed)
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
at java.net.ServerSocket.bind(ServerSocket.java:375)
at java.net.ServerSocket.<init>(ServerSocket.java:237)
at org.apache.catalina.core.StandardServer.await(StandardServer.java:428)
at org.apache.catalina.startup.Catalina.await(Catalina.java:800)
at org.apache.catalina.startup.Catalina.start(Catalina.java:746)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:284)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:415)
网猫：
$ nc -vkl 12345
Listening on 0.0.0.0 12345
$ telnet localhost 12345
Trying 127.0.0.1...
我尝试重新启动网络管理器、systemd-udevd、systemd-sysctl 和 docker。一切都无济于事。我还比较ip link|route|addr了简历之前和之后，它们是相同的。
我完全不知道问题可能是什么。有什么建议么？
所以我对 Linux 还很陌生，几天前刚刚安装了 Ubuntu，我的电脑一直遇到的一个问题是，我的 Wifi 适配器在使用大约一个小时后会自行断开连接。你们中有人知道如何阻止这种形式的发生吗？谢谢！
我正在使用 ubuntu-server 19.10，我只能 ping（根据我的尝试）google.com、youtube.com 和 ubuntu.com。
但是我不能ping，wget或者git clone来自 github.com、cnet.com、duckduckgo.com、sourceforge.net、8.8.8.8、172.217.17.142 ...
每当我尝试 ping 他们时，我都会收到以下消息：
ping: connect: Network is unreachable
如何连接到网站？
编辑：ping -n xyz得到相同的结果。
traceroute -n duckduckgo.com:
traceroute to duckduckgo.com (79.125.108.59) hops max, 60 byte packets
在 Ubuntu 18.04x86_64中，我从snap. 设置用户名和密码后（我检查了它们），长时间等待后任何登录尝试都失败：“Skype 无法连接”。
然后，我卸载了它并使用了官方网站.deb提供的包：. 又是 Skype 4.3。然而，一切都没有改变。漫长的等待后，“Skype 无法连接”。sudo gdebi skypeforlinux-64.deb
可能是什么问题？
会不会是防火墙问题？我从来没有在我的主机上设置任何端口或防火墙规则。
我有 2 台安装了 XFCE 的 Ubuntu 18.04 笔记本电脑，在不同的网络（提供商）上，位置相距约 30 公里。
配置了 SSH 连接，通过 SSH 连接到远程机器没有问题，因为他有公共地址，在路由器转发配置。
连接到远程桌面 (X) 以查看此远程桌面的活动并进行一些更改的最佳和最简单的方法是什么？如果有人需要在远程计算机上做某事，最好的方法是通过我家的远程连接向他展示如何在远程计算机上执行此操作。
如果我可以通过 SSH 连接，我是否可以仅使用来自终端的命令通过 SSH 将此服务器连接到用户的远程桌面（图形环境，XFCE）？还是来自remmina？还是需要 VNC 或 Teamviewer？
最后一个问题，如果远程计算机的 IP 地址不可用怎么办？所以只有 VNC 或 Teamviewer？
谢谢。
有一个 Ubuntu 19.10，所有最新更新都是最新的。
问题
Wifi 无法连接到安全点。密码是正确的，但弹出窗口会一次又一次地重新询问密码。
问题开始时
无线网络实际上工作得很好。但随后尝试运行：（sudo apt-get install --reinstall bcmwl-kernel-source根据https://wiki.ubuntu.com/DiscoDingo/ReleaseNotes#Known_issues）。
之后 - 无法连接。
细节
出于某种原因，无线显示为Ethernet interface。
lshw -class network
[sudo] password for obiol:
*-network
description: Ethernet interface
product: Wireless 7265
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:02:00.0
logical name: wlp2s0
version: 59
serial: 7c:b0:c2:14:71:ac
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical
configuration: broadcast=yes driver=iwlwifi driverversion=5.3.0-26-generic firmware=29.62a39462.0 latency=0 link=no multicast=yes
resources: irq:140 memory:df300000-df301fff
错误：
an 17 16:49:12 n552vw wpa_supplicant[1164]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0
Jan 17 16:49:28 n552vw wpa_supplicant[1164]: nl80211: kernel reports: NLA_F_NESTED is missing
Jan 17 16:49:28 n552vw wpa_supplicant[1164]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0
Jan 17 16:49:37 n552vw wpa_supplicant[1164]: nl80211: kernel reports: NLA_F_NESTED is missing
Jan 17 16:49:37 n552vw wpa_supplicant[1164]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0
Jan 17 16:49:52 n552vw wpa_supplicant[1164]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0
Jan 17 16:53:58 n552vw wpa_supplicant[1164]: nl80211: kernel reports: NLA_F_NESTED is missing
Jan 17 16:53:58 n552vw wpa_supplicant[1164]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0
Jan 17 16:58:51 n552vw wpa_supplicant[1164]: nl80211: kernel reports: NLA_F_NESTED is missing
Jan 17 16:58:51 n552vw wpa_supplicant[1164]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0
Jan 17 16:58:55 n552vw wpa_supplicant[1164]: nl80211: kernel reports: NLA_F_NESTED is missing
Jan 17 16:58:55 n552vw wpa_supplicant[1164]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0
Jan 17 16:59:00 n552vw wpa_supplicant[1164]: nl80211: kernel reports: NLA_F_NESTED is missing
Jan 17 16:59:00 n552vw wpa_supplicant[1164]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0
任何想法如何解决这个问题？