16.04 SERVER USING vsftpd using tls getting ECONNREFUSED

I have 16.04 on a hosted server with a static IP. I have the ufw off for the moment to get ftp working. I configured vsftp, then I added the chroot capability. It was working fine-sign in with a user and they are limited to their directory–singing in from a remote location.

Next, I am attempting to configure TLS to improve security. I follow the instructions and generate the key, then turn on the options in the /etc/vsftpd.conf file (more details below)

I attempt to connect via Filezilla and I get the error Connection attempt failed with “ECONNREFUSED – Connection refused by server”

I see other similar questions, and I have tried the answers on similar questions with no result.

Following is what I added to the vsftp.conf to enable tls after successfully testing ftp without tls.

ssl_enable=YES

allow_anon_ssl=NO

force_local_data_ssl=YES

force_local_logins_ssl=YES

ssl_tlsv1=YES

ssl_tlsv2=NO

ssl_tlsv3=NO

rsa_cert_file=/etc/ssl/private/vsftpd.pem

rsa_private_key=/etc/ssl/private/vsftpd.pem

Any ideas?

Mounting USB HDD on (Sagemcom 5566 Router/Bell Hub 3000) Ububtu 16.04

I can’t auto mount the Router USB HDD on New supplied Fibre Router.

Nautilas smb://192.168.1.1 does work manually and Ctrl-L shows it as smb://192.168.1.1/iomega%20hdd/ and all access is available this way.

Fstab has //192.168.1.1/USB_Storage /media/NetDrive cifs user,guest,sec=ntlm,uid=dennis,exec 0 0 set up in it butdoesn’t mount the drive.

The error I get is: mount error(6): No such device or address Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Going through that manual has left me trying different names for the USB_Storage, but I have run out of names to try.

Logging into the Sagemcom Router shows: Device name as Iomega HDD, Port=USB-, Type=USB 0.0

This all used to work fine on a Netgear R6300 Router but the Sagemcom 5566 would seem to have some different method to identify the USB ports.

Any Help would be greatly appreciated.

I can’t go back to the other router as this one has Fibre right into the router for my service.

vmwgfx error in kernel log on Ubuntu 16.04

This is my kernel log. Near end you see:

[ 24.927057] WARNING: CPU: 0 PID: 376 at /build/linux-bKdGSR/linux-4.4.0/drivers/gpu/drm/vmwgfx/vmwgfx_dmabuf.c:301

I found it when I investigated my GNOME problem. Which stopped working suddenly on my VM. Before that it wasn’t coming up only for one account. In Xorg log we see that access to fb0 is denied. So I checked the server log and found this so decided to fix this first. From what I understood there is a problem with VMWare driver module.

Can I update or reconfigure this kernel module?

Oracle Database 12c Re2 installation, directory permissions (Ubuntu 16.04)

I’m trying to install oracle database 12c Re2 on my Ubuntu 16.04, but I failed.

When choosing the directory, where the Oracle Base, the Software and the Database file should be located, I got the error INS32012 (check your directory permission).

I used following install guide until the GUI appears (https://medium.com/venturenxt/install-oracle-database-12c-on-ubuntu-16-04-c081d51c0f9d). At that point my configuration changes, because I use a Desktop Class. Nevertheless, I also tried with the Server Class and it didn’t work neither.

Could somebody tell me, if there is something missing in this guide? How can I solve this problem?

Thx

16.04 Delayed Recogntion of External monitor from docking bay

16.04 in a docked HP 8440p laptop recognizes the external displayport monitor at boot.

The machine is often left on at night, however the monitor is turned off. In the past, the system would immediately recognize the monitor, when the monitor is powered up. Now when the monitor is powered on in the morning, the system does not ‘see’ the external monitor (monitor indicates no signal and enters power saving mode). I tickle the Ubuntu machine with the external keyboard (Num Lock LED indicates machine is responsive). Docking bay’s LAN LED flashes.

I retreat to my Windows box to start my day and 16.04 will eventually discover the monitor.

  1. What setting can be manipulated to restore immediate recognition of the monitor?
  2. Is there a process (i.e. keyboard strokes) that will prompt the system to recognize the displayport monitor?

It would be nice to know what caused the change (delayed recognition of the monitor).

16.04: gdm3 WaylandEnable=false and lightdm only load sometimes

I am happy to use either gdm3 or lightdm, but neither are stable on my Ubuntu 16.04 system, they will work for either one or several boots after I take corrective action, but inevitably this results in the greeter not loading – the last few times (at least) I noticed this was immediately after I did a sudo apt update. The graphics card on my Intel Core i5 system is an Nvidia GTX 970, and I manually installed nvidia-driver-415 when I could not load a greeter as soon as I had installed.

Searching here and elsewhere, I have tried many things to resolve this, which I will outline below. If you know something else I can try – to get either greeter stable – please let me know.

gdm3

Even with WaylandEnable=false uncommented in /etc/gdm3/custom.conf, I could never login, instead of the greeter I would see either a black screen or graphic distortion like a black screen with some pink lines across the top, and I am only able to login setting nomodeset.

With gd3 not working, I tried lightdm, and on encountering similar issues switched back to gdm3 again:

sudo apt-get install gdm3 sudo dpkg-reconfigure gdm3 

This seemed to work – kind of, for the first few days I could boot most of the time. I have quiet splash permanently removed from my boot options, and boot was sometimes hanging on Started NVIDIA Persistence Daemon as below:

gdm3 fail 1

Another time with gdm3 I saw the following output instead of the greeter:

gdm3 fail 2

gdm3 fail 3

lightdm

When I use lightdm instead, and the greeter does not load, I see a flashing black screen with a single white underscore top left. I can never get to a TTY using ctrl + alt + f3/f4/f5, REISUB does not work, so I hard rebooted, the greeter loads with nomodeset, and from there without logging in I switch to a TTY and I have tried what I outline below. Sometimes if I just reboot again without nomodeset the greeter will just load properly, without my changing anything.

Observing these permissions:

-rw-------  1 dusf dusf      56 Jan  7 17:38 .Xauthority -rw-------  1 dusf dusf   15886 Jan  7 17:38 .ICEauthority  drwxrwxrwt 16 root root 4096 Jan  7 17:45 /tmp 

I input the following, and could login normally next reboot:

sudo chown dusf:dusf .Xauthority sudo chown dusf:dusf .ICEauthority sudo chmod a+wt /tmp 

The next time the issue occurred I input the following, and could login next reboot:

sudo dpkg-reconfigure lightdm 

In cat .xsession-errors, I noticed the following line, which I thought could be relevant considering I see an underscore instead of a greeter?

_=/usr/bin/dbus-update-activation-environment 

Next temporary fix:

mv .Xauthority .Xauthority.bak 

Again:

sudo apt-get purge lightdmsudo apt-get install --reinstall lightdm sudo apt-get install gnome 

After a sudo apt upgrade a few days ago with the same issue recurring I input all of the following and everything seemed fine for a few days:

sudo apt upgradesudo apt purge lightdm sudo apt purge gnome sudo apt purge nvidia* sudo apt remove nvidia-driver-415 reboot sudo apt purge nvidia-* sudo apt install nvidia-415 sudo apt install nvidia-driver-415 reboot sudo apt purge xorg-* xserver-xorg sudo apt install xorg xserver-xorg sudo dpkg-reconfigure xorg sudo apt purge ubuntu-gnome-desktop sudo apt purge gnome-desktop-environment apt install ubuntu-gnome-desktop sudo apt install ubuntu-gnome-desktop sudo apt purge lightdm sudo apt install --reinstall lightdm 

The next time the issue occurred I noticed in my .bash_history the last commands I input were:

sudo apt update sudo apt upgrade 

and I uploaded the following logs:

/var/log/lightdm/lightdm.log

cat /var/log/kern.log

cat .xsession-errors

I read adding an xrandr line to some files may be the next step, but the actual lines seem to be system specific, and their are recommendations on adding them to different files.

How can I begin to resolve the issue, either with gdm3 or lightdm please?

Ubuntu 16.04 cannot connect to wifi: The Wi-Fi network could not be found

This has been driving me nuts. Here is a sequence of events that happened (to the best of my memory):

Wifi was working fine on my Ubuntu 16.04 computer. But after installing security updates (using unattended-upgrade), somehow the network manager could not detect any Wifi. I tried rebooting the system, then the network manager showed “device not managed” for both Ethernet and Wireless connections. According to this thread and many alike, I modified

/etc/NetworkManager/NetworkManager.conf 

and changed the managed=false to managed=true, and then restarted the network-manager service. This did make the “device not managed” go away, and I did see the list of Wifi’s in the drop-down menu of network manager. However, when I tried to connect to any one of them, the network manager just waited for a while and eventually failed to connect. It was almost as if those listed Wifi names are fake.

I then tried to use the command-line tool nmcli and see if there is any useful error messages. Notice that all this time managed=true is set. First, I ran

nmcli device wifi list 

and I see a list of wifi spots that seemed pretty normal. Then I tried

nmcli device wifi connect <SSID> password <PASSWORD> 

with SSID and PASSWORD being the wifi spot I’m trying to connect to. Then, after a few seconds wait, an error shows up:

Error: Connection activation failed: (53) The Wi-Fi network could not be found 

Additional Question Regarding the “device not managed” problem, it is strange to me that (1) it occurs at all (2) setting managed=true is the correct fix. I have checked the NetworkManager.conf files on several other 16.04 machines I have access to, and they all have managed=false and are still able to connect to the Internet. What’s an explanation of this?

I sincerely appreciate your help!

Alsa not properly detecting front panel audio jack on Ubuntu 16.04

I often switch between between my headphones and speakers and this is the usual behavior that’s supposed to happen:

  • If I unplug my headphones which is connected to the front panel, the sound output will automatically switch to the speakers which are connected to the back panel.
  • If I plug my headphones back in the front panel, the speakers connected to the back panel will automatically mute itself and I’d get sound output from my headphones. The volume profile will also switch.

I believe that’s the default settings because I don’t have any issues with 2 other computers with almost the same configurations.

This problem happened after I unsuspended my computer, so most likely not caused by a system update.

What happens now is :

  • Unplugging whatever connected to my front panel will not mute my speakers whatsoever.
  • The only way to get my headphones working is switching the output device to “headphones” in Pulseaudio Volume Control. Even though it displays as unplugged, I’m still getting audio output from it. This has been tested with different devices.

enter image description here

Then I’d get audio output from both my speakers and my headphones. The auto-mute option in alsamixer does nothing. I’ve tried using the gnome version and it shoots a
** (gnome-alsamixer:12461): WARNING **: gam_toggle_set_state (). No idea what to do for mixer element "Auto-Mute Mode"!

error. I’ve tried restarting, reinstalling Alsa and Pulseaudio but the problem was still happening.