[00:10] so I just installed ubuntu [00:10] and did `sudo apt update && sudo apt upgrade`` [00:11] and it's telling me that grub failed to install to the following devices [00:11] I tried to reinstall it and it does the same thing [00:11] I've never come across where something just didn't install [00:12] especially grub [00:12] can anyone help? [00:12] how do you say yes to "Are you sure you want to continue connecting (yes/no/[fingerprint])?" in gftp? [00:12] its in the log window [00:19] bumblefuzz we rather need more info to help you [00:19] what would you like? [00:19] this is all the info I have [00:20] give us the output to "and it's telling me that grub failed to install to the following devices" I'm pretty sure there is more than that [00:20] GRUB failed to install to the following devices: │ │ │ │ /dev/sda2 │ │ │ │ Do you want to [00:20] continue anyway? If you do, your computer may not start │ │ up properly. │ │ │ │ Writing GRUB to boot device failed - continue? [00:20] bumblefuzz do you still have a usb stick or so connected? [00:21] no [00:21] I'm booted in the new install [00:21] just trying to run update and upgrade [00:21] and this came up [00:21] it's brand new [00:21] bumblefuzz this is a bios/legacy install or? [00:21] UEFI [00:23] can you give me the output of /etc/fstab in a paste (paste.ubuntu.com) [00:24] https://pastebin.ubuntu.com/p/yRPp42PMtr/ [00:25] bumblefuzz so I guess when you 'sudo update-grub' the same error gets displayed? [00:26] grub-probe: error: cannot find a GRUB drive for /dev/sdc1. [00:26] grub-probe: error: cannot find a GRUB drive for /dev/sdc1. [00:26] it made it to done [00:26] after those errors [00:27] so what device is sdc? [00:27] I'm reflashing an ubuntu install disk [00:27] 16gb USB drive [00:27] cause I might have to reinstall everything [00:27] okay, so that error is fine [00:27] it should work, still not sure why you got that error :/ [00:28] it seems like that worked [00:28] bumblefuzz the only thing I can think of, grub thought it was a bios/legacy install and thats why it tried to install the 'mbr' part [00:28] but I literally booted into a fresh install and ran ` sudo apt update && sudo apt upgrade` and landed on this GRUB error [00:28] how can I make a new install if I can' upgrade [00:28] can't* [00:29] what do you mean by you can't upgrade? packages or distro version? [00:29] this is very simple: I installed ubuntu [00:29] then I booted the new install [00:30] and the FIRST thing I did was run `sudo apt update && sudo apt upgrade` [00:30] then I had this GRUB error [00:30] if I cannot upgrade packages, how am I supposed to install ubuntu [00:30] ?? [00:30] I mean try to boot (after having the install usb) and test it out. imho it should be fine now. [00:31] but the upgrade is stalled on this grub error [00:31] i guess, if you want to use the whole disk that the installer formats the whole disk, to make sure to start from a clean plate [00:31] grub has not been updated [00:31] even if you rerun apt upgrade? [00:33] I don't know what's going on [00:33] every time I run upgrade, it lists a bunch of packages that have been kept back [00:34] post the output to a paste, so I can read it [00:34] eading package lists... DoneBuilding dependency tree Reading state information... DoneCalculating upgrade... DoneThe following packages have been kept back: libnvidia-cfg1-440 libnvidia-compute-440 libnvidia-compute-440:i386 libnvidia-decode-440 libnvidia-decode-440:i386 libnvidia-encode-440 libnvidia-encode-440:i386 libnvidia-extra-440 [00:34] libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-gl-440:i386 libnvidia-ifr1-440 nvidia-compute-utils-440 nvidia-driver-440 nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-utils-440 xserver-xorg-video-nvidia-4400 upgraded, 0 newly installed, 0 to remove and 18 not upgraded. [00:35] https://paste.ubuntu.com/p/nNQ6nVjpTD/ [00:36] bumblefuzz what happens on a 'sudo apt full-upgrade' don't accept, paste it on paste.ubuntu.com [00:36] that appears to be running [00:36] why wouldn't the usual command work? [00:36] I've never had this much trouble on a fresh install [00:37] I guess the nvidia driver is acting up, full-upgrade is allowed to remove packages [00:37] upgrade doesn't [00:38] I'm going to try and reboot [00:45] Hello [00:45] I was wondering if you could please help me getting a bluetooth multi-touch mouse to work with Lubuntu? Thank you. [00:48] some people suggested selecting two-finger in the touchpad settings, however, that option is greyed out so I can't select it [00:48] On other devices and in Windows 10 the touch-surface mouse works normal [00:48] However, in Lubuntu 20.04 LTS I can't seem to get it to work the same way for scrolling [00:48] Any suggestions would be much appreciated. I've been trying to get this to work for weeks. [01:59] still can't get anything but a black screen after grub. made a post here https://ubuntuforums.org/showthread.php?t=2453703&p=14000383 [02:00] is there any kind of... driver diagnostic or something I can do through SSH that might shed some light? [02:04] GunArm_: do you have a live OS image handy? Does video output work after GRUB for it? [02:04] let me see I probably have one in a drawer already [02:05] GunArm_ I would also say, that maybe post the whole /etc/default/grub file (at least here in a pastebin) [02:07] https://pastebin.com/mU1315HG [02:12] GunArm_ do you have a samsung ssd? [02:16] I'm running ubuntu 20.04 desktop pulled from the main website today. I installed it on a new inspiron 7300 2n1 convertible laptop/tablet. The stylus worked fine in all orientations right up to after the fresh install did a system update and reboot. [02:17] Now, after orienting the device, the screen will flip to the new orientation but the stylus position is mirrored in all but the default orientation (where it works fine) [02:18] darkdigitaldream, i have mostly no idea, but did you install the oem ubuntu version? (i guess it's a certified laptop?) [02:18] quadrathoch2: interesting question, yes. although I also have a WD NVME as the boot drive, and that is the one that has caused me problems (it's why I have that one option set in grub already, or it would lock up in some kind of low power mode) [02:19] GunArm_ ahh okay, as the arch wiki specifically says samsung ssds and only kernel 4.10 (which is pretty old) [02:19] yeah that was a nightmare to figure out when I was first building this machine === zbenjamin is now known as Guest6166 === zbenjamin_ is now known as zbenjamin [02:19] I can imagine :/ [02:19] took me literally weeks to get it working [02:20] but back to topic, I guess you edited the boot entries in grub and not the file? GunArm_ [02:20] yeah, booting is a slow process because of the raid bios, so I don't want to have to reboot twice for each test [02:21] also it's pretty easy to just see like, with an option, hit f10 and then it looks like the backlight turns off on the screen [02:21] booting with a live disk is a good idea, I just I guess will need to make one since I can't find one around [02:21] yup :). still not sure why you even installed the closed source nvidia driver, but I guess the nouveau wasn't working? GunArm_ [02:22] GunArm_ yeah that's a very good idea [02:22] quadrathoch2 oh that's easy to explain, because I have no idea what I'm doing and I'm throwing things at the wall to see what sticks ;) [02:22] quadrathoch2 I see no official OEM listing/distro for this device [02:22] is nouveau the open source driver? [02:22] haha xD. that gpu is so old that the open source driver works perfectly fine [02:23] The part that I find most interesting is that this works before a software update. Something in the update breaks this feature [02:27] darkdigitaldream are we talking about 20.04 package updates i assume? [02:30] quadrathoch2 yes. The iso install works fine. It works fine after a reboot. Then it quickly suggests updates and a reboot, after which the feature breaks [02:30] installer* [02:31] darkdigitaldream, damn so means that a package upgrade breaks the pen support :/ [02:32] could you look at the logs in /var/log/apt/history.log and post it to paste.ubuntu.com darkdigitaldream [02:34] it looks like in that sftp docker image you have to map your users to host users otherwise you cant give them permissions [02:35] quadrathoch2 https://paste.ubuntu.com/p/f39qvmHdcS/ [02:39] lots of libwacom updates by eyeballing the list. Not sure if thats a lead or not [02:44] darkdigitaldream the only things I can see, a small part of the xserver was updated, and the kernel. the wacom stuff was the stuff on the ISO which was installed during installation [02:45] Just tried installing recommended nvidia drivers via "ubuntu-drivers autoinstall". Ended at this: update-initramfs: Generating /boot/initrd.img-5.4.0-53-generic \n E: Could not configure 'libc6:i386'. [02:47] alazy did you activate the 32bit architecture? [02:48] quadrathoch2: No. I installed 64 bit OS. What am I supposed to do? [02:48] hmm, so the good news is there are only a few spots this issue can come from. The bad news is its xserver and the kernel :/ [02:48] 'sudo dpkg --add-architecture i386' 'sudo apt update' and then redo the 'ubuntu-drivers autoinstall' [02:48] alazy ^ [02:49] darkdigitaldream and or ;) [02:49] darkdigitaldream the kernel would be the easiest to test out, as the older version should still be installed, you would just need to reboot and select it in grub [02:49] oh, thats a good idea [02:52] Did that. Ubuntu-drivers autoinstall didn't seem to do anything. Just read list, built dep tree, read state info, and then told me 0 upgraded. [02:53] Should I try to remove what was autoinstalled then reinstall? [02:54] could you try 'sudo apt install -f' [02:54] same nothing [02:55] alazy yup that would be probably the best bet then [02:55] (removing and reinstalling) === BrianG61UK__ is now known as BrianG61UK_ [02:57] is it possible to recover any part of an overwritten file? [02:58] probably not mindofmateo [02:58] sudo apt install --reinstall nvidia-driver-450-server? [02:59] alazy should do it [03:00] I am not 100% sure with the nvidia stuff :/ [03:02] quadrathoch2: thanks, I think that worked. [03:03] just look it up, if it really did it ;) [03:09] okay, so the old kernel has the same problem as the new. [03:11] darkdigitaldream damn, so now only xorg could be the culprit, or some other package I have no idea about :/ but I guess xorg [03:12] quadrathoch2 hmm. I also found another interesting tidbit: my finger on the screen works just fine. Its the stylus that inverts [03:15] very interesting :). sadly I wouldn't even know at which package to report a bug like this :? darkdigitaldream === [1]MrMobius is now known as MrMobius [03:16] Thanks for the advice all the same. I have a few more things to try, but we've narrowed it down much better than I'd of managed myself. [03:39] exit [05:23] hello, i am can anyone help me with an emoji issue? [05:23] https://github.com/ryuukk/read_me_emoji_2 the check mark should be a green square with a square arrow [05:24] but for some reasons it is displayed as a white mark on linux [05:24] on macOS and windows i get the right one [05:24] https://files.gitter.im/5d6fa72cd73408ce4fc9fa9c/DDiT/test.png it should look like the one on the left === PowerTower_121 is now known as PowerTower_120 === kinghat4 is now known as kinghat [07:05] looks like a github issue [07:28] Unlike 18.04, my current 20.04 complains "Mouse battery below 10%" every time my mouse wakes up from hibernation. It hibernates after ~2 minutes of inactivity, so Ubuntu complains about it ~40 times/day in my use, which is most annoying when watching a movie and setting a cup on the table, waking the mouse. I want to limit the complaints to a [07:28] minimum interval of ~1 day. How do I do that? [07:28] change to a fresh battery? [07:31] There's nothing wrong with this battery - there's still ~2 months of juice left. Anyway, that's irrelevant in my attempt to improve Ubuntu. Complaining to the user that often makes no sense in any situation. [07:33] i have no clue what part of the desktop is responsible for this warning, wait for somebody who might know, but be aware it is very quiet here for another couple of hours [07:33] *it [07:35] in the meantime, try googling the actual message you get [07:36] Thanks. [07:37] around 11-12cet there should be more people here [08:49] How to know which display driver is currently in use? [08:50] zetheroo: sudo lshw -C video [08:51] lotuspsychje: Thanks, what does this mean " *-display UNCLAIMED" ? [08:52] zetheroo: unclaimed means your driver has not loaded for your graphics card [08:53] zetheroo: usually dmesg will spit out errors if the driver loading failed [08:54] I ave two gpu chipsets - Intel and Nvidia - and currently the Intel one seems to be active and the Nvidia not. I already installed the Nvidia 450 driver (tested) [08:55] https://paste.ubuntu.com/p/2GbpqrN3gJ/ [08:55] zetheroo: try installing another driver version first, see if you can get the driver loaded [08:56] zetheroo: ubuntu-drivers list, to see wich available [08:57] I installed the driver via the Software & Updates gui - was that wrong? [08:57] ubuntu-driver list https://paste.ubuntu.com/p/kWH843MYqr/ [08:58] do I have to manually switch somehow from one gpu to another .... ? [08:58] zetheroo: try switch to 435 [09:00] ok [09:02] strange - a 'Configuring Secure Boot' windo just popped up as the Nvidia 435 driver was being installed [09:02] wants be to set a Secure Boot password!? [09:04] https://ibb.co/3YfZ5yk [09:08] ok driver installed ... I guess a reboot is required? [09:09] no info saying a reboot is needed, but the Nvidia device is still unclaimed [09:15] on reboot, before the GRUB menu, I got an ugly blue screen asking me if I wanted to continue to boot or enroll MOT ... no idea what that was about ... I hope that isn't going to show up with every boot now : [09:15] Nvidia is still unclaimed [09:18] zetheroo: you should have enrolled the MOK [09:19] the instructions are given during driver install [09:20] ducasse: ah ok ... my bad [09:20] any idea why this did not happen with the 450 driver? [09:21] ït's a secure boot thing, you could also disable that [09:22] under secure boot, kernel and modules need to be signed. third-party modules aren't [09:23] i thought this had been fixed, but apparently not [09:23] hmm ok [09:24] what does 'mokutil --sb-state' say? [09:24] SecureBoot enabled [09:26] right. disable that or run 'mokutil --enable-validation' and reboot, following the steps [09:26] ok [09:27] Failed to request new MokSB state [09:27] did you set a password? [09:27] I entered my password twice correctly [09:27] yes [09:27] password = password [09:28] then i guess you get the prompt on reboot [09:28] ok [09:28] if not try --disable-validation [09:32] rebooted but no blue MOT screen [09:33] should I disable and then enable validation? [09:38] ah 'sudo' was needed for the '--enable-validation' command ... ok rebooting again [09:51] hi. Inside a project i have a symlink inside a folder, which is a package. I am wondering how to ls ./vendor/me/bundle ? [09:51] ok, I ended up just disabling SB in the BIOS [09:51] or ls ./vendor/me/bundle/some_folder [09:52] Nvidia display device is no longer unclaimed [09:52] zetheroo: great, you should be able to switch between them in bios or software [09:53] ducasse: how do I know which one is in use atm? [09:53] or is it just done automatically ... [10:16] ...maybe is because some incompatibiliy of ls inside docker of a symlink created on a host [10:29] Battery shows up as "Fully Charged" in drop-down menu, but in Power Settings it's not https://ibb.co/Wnks7gn [10:29] https://ibb.co/7gWHNWL [10:29] almost seems that Ubuntu thinks there are two batteries ... !? [10:30] upower output: https://paste.ubuntu.com/p/yG79Gc6bGf/ [10:43] zetheroo1: what does 'ls /sys/class/power_supply/' say? [10:45] AC BAT0 [10:46] ok, 'cat /sys/class/power_supply/BAT0/status' [10:47] Charging [10:47] right, that's what i would trust [10:48] so I guess the GUI is a bit messed up ... [10:48] i dunno, i don't use gnome [11:02] Hello. As far I understand, every interim release (non-LTS, say 20.10), the non-LTS kernel is "backport" to the LTS release throw the HWE stuff. I didn't find the 20.10 kernel on 20.04 LTS HWE. Am I missing something ? [11:03] polichouz: it takes quite a while for it to be backported, tested and released [11:03] like, months [11:04] it will then be released as a point release [11:05] 'plug in a dongle to use bluetooth' [11:05] it was working and now it just stopped. any suggestions? [11:08] i did google and it [11:08] ducasse, Thanks. I'll monitor the next point release then. Still T.B.D. the last time I've checked. [11:09] hey guys. my blue tooth decided not to work today. tried https://itectec.com/ubuntu/ubuntu-no-bluetooth-found-plug-in-a-dongle-to-use-bluetooth-ubuntu-18-04-1-lts/ any other suggestions? [11:09] yesterday === jelly-home is now known as jelly [12:51] eliyahutbr: Do you have another computer to test the dongle on? Sometimes they just die. [13:01] Hi all [13:01] hey [13:01] hey [13:02] i fresh install 20.04.1 HP EliteDesk 800 G1 SFF and Front Mic Jack doen't work :-( [13:05] someone can help? [13:17] hi, i am running a web server with ubuntu 18.04.5 LTS and whenever I login with SSH, it keeps suggesting me to upgrade to 20.0.1 LTS using "do-released-upgrade". I am a bit scared that my apache / php / etc configuration will be messed up. how safe is an update like that? [13:20] Starship8014 too many deltas to consider. Make a backup/test restore, then move on to upgrade. If all fails, restore. [13:22] Starship8014: As XV8 beat me to: If you have a backup that you know how to restore then you can do the upgrade. Based on anecdotal evidence the success rate for upgrading from 18.04 to 20.04 is 80% [13:23] i have made a snapshot from my system and my hoster allows me to setup a new box based on that snapshot. I could do that, test the upgrade there and if it works, do it on my live as well. maybe that's a good way to go? [13:31] hi. I am trying to use manually openvpn and make it log to /var/run/piavpn-manual. but it fails with a permission error; why ? is it a apparmor related issue ? === jeddo- is now known as jeddo [13:34] solsTiCe: Does it say what permission it is erroring on? [13:35] it says :' --up script fails with '/var/run/piavpn-manual/openvpn_up.sh' but the script is executable [13:36] oh I guess something oes not like executalbe in /var/run [13:37] ah /run is mounted with noexec [13:38] Why aren't ram block devices listed under /dev? [13:39] or are they listen as something other than ram? === mateen1 is now known as mateen [14:27] Hi [14:28] hello [14:28] I have a dedicated distant server running Ubuntu. I want to occasionnally backup data from my local computer to it [14:28] what would you use? (~ 1 TB of data) [14:29] I'd like that even if someone hacks my distant dedicated server / gains root access, he *cannot* access my data [14:29] Do you have any idea? [14:30] rsnc ? [14:30] rsync [14:31] ikonia, but how to be sure if someone has root on the distant server, he cannot read the data? [14:32] ahylight: maybe something like vaults? https://learn.hashicorp.com/vault [14:43] mefistofeles, I'll read about this, thanks! [14:43] mefistofeles, I just posted the question here with more details: https://superuser.com/questions/1602585/backup-on-a-distant-dedicated-server-such-that-even-if-someone-gets-root-hack [14:44] ahylight: encrypt it [14:45] ahylight: in reality how senensitive is the data [14:45] if it's that important, should you really be treating it this casually [14:45] it's encrypted locally [14:46] ikonia, I specifically want that the data is totally *impossible to use* on distant server [14:52] ahylight: so if it's encypted locally, you're copying an encypted resource, root ont he remote server doesn't matter [14:53] ikonia, the hard drive is encrypted, but when i open the computer and access to the files, they are not encrypted [14:54] once the password is entered, you have normal access to the files [14:54] i.e. if you send them via rsync etc. the destination will be *files*, normal files [14:54] so encrypt the target [14:55] so i need to enter a password via ssh etc. [14:55] again - if it's that important should you truly be treating it this casually [14:56] so if someone has a root access on the distant server, he can get the decryption key, do you see what i mean? [14:56] he can't get the decyrption key [14:56] why not? [14:56] what do you mean by "encrypt the target"? [14:56] more precisely [14:57] make an encypted file and sync the file [14:57] but again - if it's that important should you really be just 'throwing it' into a remote server [14:58] ideally for backups drives it should be ok if they are stolen [14:58] example: i have an encrypted 2.5" external usb hard drive with all this data [14:59] I *could* lose it in front of my house, and anybody could steal it, it would be ok, since no key is available for them [15:34] how can i start lynx and load url from clipboard? [15:42] RoseBus: lynx $(xclip -selection clipboard -o) # install xclip === Mollerz4 is now known as Mollerz [15:46] I'm trying to run the command sudo apt-get install linux-headers-5.4.0-53-generic:i386 but I get an error that no package could be located. What should I do? [15:47] does that package exist ? [15:47] I thought 32bit was gone [15:47] ikonia, oh [15:48] It seems like Ubuntu 20.04 keeps automatically adding printers from my network. How can I stop it from doing this? [15:48] I'm sure it's not adding them [15:48] they are advertising themselves [15:48] They show up in my printers list, and come back immediately if I remove them [15:49] I only want printers I explicitly add to show up [15:49] probably because they are advertising themselves [15:50] I basically have 3 copies of the same printer, because I have another machine running CUPS that has it added and also shares it using AirPrint. The third is the printer itself. This is absolutely stupid. [15:50] I only want my printer to show up once [15:50] then stop the other hosts from advertising it [15:50] ikonia: If I do that, it'll be impossible to print to it from our mobile devices [15:50] Some_Person: https://askubuntu.com/questions/918462/remove-printer-added-notifications-from-gnome-3/921289#921289 [15:50] turn off the bonjour service [15:51] Some_Person: so you want it to advertise itself globally as it's meant to....but tell this one machine to ignore it being advertised [15:51] ikonia: Pretty much. I want my desktop to not give a crap about advertised printers [15:51] Some_Person: turn off the bonjouf service on your desktop [15:51] How do I do that? [15:52] Some_Person: please see the link I just posted [15:52] can't remember what the linux compatible bonjour service is called, have to google [15:52] ahhh there is is, dnssd [15:52] dns service discovery [15:52] ikonia: avahi. But the link I posted will work as well [15:53] ikonia: That solution does not seem to work. Printers still come back automatically [15:53] ikonia: Some_Person: I had the same issue and following the instructions in the link I posted worked for me [15:53] Some_Person: what solution [15:53] Sorry, that was meant for leftyfb === BromaxSux1 is now known as BromaxSux [15:57] Some_Person: maybe you need to restart cups after the change in the conf file [15:57] pavlos: I tried that. No dice [15:59] Hello everyone [15:59] I've also tried stopping cups-browsed. No dice there either [16:00] Some_Person: you set "BrowseProtocols none", restarted cups, and they still advertise? [16:01] pavlos: Correct [16:01] They still get added to my system automatically [16:01] Some_Person: can you paste, cupsctl [16:02] https://pastebin.ubuntu.com/p/m78mZ7Kn5p/ [16:11] Some_Person: maybe stop/disable that service, sudo systemctl disable cups-browsed [16:11] pavlos: Tried that === ijohnson is now known as ijohnson|lunch [18:08] I keep getting a dialog box that says "Package operation failed - The installation or removal of a software package failed" after the updater runs ... any clues? Ubuntu 20.04 [18:10] rjwiii do you have any custom PPAs added? [18:28] hi all, I just installed Ubuntu 20.04 desktop but I cannot figure out how to get the wifi started up or connected. I cannot see any options for the wifi adapter but lsusb gives me - Bus 002 Device 005: ID 2357:011f TP-Link 802.11ac WLAN Adapter [18:28] can anybody help me get this working? :) [18:31] Some_Person I have that same issue, tried mostly everything I found on the internet. My guess is, gnome is doing something really weird. I get that message every 10 mins >< [18:37] mboard, try this : https://gist.github.com/jeremyb31/c7e562e822bbe24df58e31487cb74e9c [18:38] mboard: https://github.com/aircrack-ng/rtl8812au Secure boot needs to be disabled [18:48] hi [18:48] ubuntu 16.04LTS : arping says "unknown host" no matter what know hosts from the router's list I feed it. what's wrong? [18:48] even sudo [18:50] ioria and jeremy31 thank you both for the links but I am unable to get this to work, the first link with the git is missing the bash script and the second link is a little confusing for me [19:03] hello channel. I have an issue that I am unsure when it showed up, possible that was caused from upgrades over the years. The root of the problem is that Apache2 does not properly start on reboot, but will pass config check and start properly once booted. It appears that it is being started from init.d, i dont have a fresh installed 20.04 but wonder if it should be using systemd? [19:05] sudo systemctl enable apache2.service [19:05] or sudo systemctl enable apache.service [19:05] not sure how it's named [19:06] chemist^, is that all need to do to convert from the two, or then delete the /etc/init.d/apache2 ? [19:07] maszlo, convert what? from what? [19:07] init.d to systemd [19:07] Does this command give you any output? [19:07] sudo systemctl status apache [19:08] apache2.service sorry [19:08] "sudo systemctl status apache2.service" [19:08] chemist^, should i have it in the error state after a reboot when it fails? [19:08] I just want to see if systemd finds the service and shows it's status [19:09] doesn't matter if it's running or not [19:09] yes it does show the status from systemctl [19:10] then just issue the command: sudo systemctl enable apache2.service [19:10] and it will be enabled on boot [19:10] you can reboot afterwards and check again with "sudo systemctl status apache2.service" [19:10] sorry maybe not clear on the issue. [19:11] you said that when you reboot your machine, apache does not start automatically [19:11] it is attempting to start on reboot, but appears that is not loading in order. like starting before networking and failing [19:12] that's really strange...have you checked any system logs? [19:12] or apache logs? [19:12] yeah would say could not bind to port.. but then if i told it to start it just worked [19:13] which is why wondered if cause was from the /etc/init.d/apache2 script === denningsrogue7 is now known as denningsrogue [19:14] maybe will move that script out of theser and see if tell it to enable see if it builds the same thing [19:25] chemist^, that appears closer. now on boot it does start, but looks like it is trying to host a http site over https port [19:26] chemist^, the status logs complain that cannot resolve the hostname.. if do a systemctrl restart no errors. still seems like it is loading before networking is up [19:31] what version of ubuntu are you running? [19:31] maszlo, [19:32] 20.04 [19:32] and you use /etc/init.d to run apache? [19:32] maszlo: /etc/init.d/apache2 does exist there, but you should just ignore it. [19:32] use systemctl exclusively [19:34] maszlo, also..."trying to host a http site over https port" doesn't make much sense ... can you pastebin the content of your /sites-enabled/ configs? [19:34] interesting.. i just found the fix by modifying the script from After=network.target to After=network-online.target [19:34] which script? :D [19:35] the file /etc/systemd/system/multi-user.target.wants/apache2.service [19:36] that'll be a symlink to /lib/systemd/system/apache2.service [19:36] which shouldn't be edited, but a clone of it. [19:39] okay I reverted it. rebooted and can get the ssl error again. SSL_ERROR_RX_RECORD_TOO_LONG it shows that it is https:// but the browser does not show that it is encrypted [19:40] maszlo, please paste your sites-enabled config file [19:41] maszlo, /etc/apache2/sites-enabled/*.conf [19:41] sure.. one second [19:41] also...use nginx :D it's simpler to configure and has many features that apache doesn't [19:42] the config syntax is fairly similar - you would get used to it in no time [19:44] https://pastebin.ubuntu.com/p/6HCmFhx552/ [19:45] strange config :D [19:49] do an apache2ctl configtest http://manpages.ubuntu.com/manpages/focal/man8/apache2ctl.8.html [19:50] normally, you'll enable mod_ssl by running a2enmod ssl [19:50] (that's for openssl support. there's also gnutls, i think) [19:50] the test reports Syntax OK [19:51] maszlo, what about "a2enmod ssl"? [19:53] it says module ssl already enabled [19:53] i think i need to reboot it to be in the bad state again for this test [19:54] i have already ran systemctrl reload apache2 [19:55] i guess very dirty fix would be a crontab entry to do that @reboot [19:55] maszlo, this is what one of my old apache configs looks like: https://pastebin.ubuntu.com/p/HgPjbzdbf2/ [19:55] reload/hup is sufficient to reload the configuration files after you edited them, but not to load new modules [19:55] you have your fullchain also configured as your certificate....is this correct? [19:56] thats fine [19:58] hmm so if doing the reload fixes it and not related to the modules itself does that tell anything? [19:58] if you look at that site now can see that is giving error [20:00] but the error SSL_ERROR_RX_RECORD_TOO_LONG means something is not configured right on your server [20:00] try modifying your sites-enabled config file following the example I pasted [20:01] ---> https://pastebin.ubuntu.com/p/HgPjbzdbf2/ [20:01] that is really weird. the fact that it does not do that when change the systemd file to use After=network-online.target and doing systemctrl reload fixes it [20:02] you're missing also "SSLEngine On" [20:02] maszlo, magic :D [20:03] chemist^, okay i will make a new sites-avail conf with that as template [20:03] maszlo, if it's not too much trouble...backup your existing sites-enabled config and try the one I pasted above - change the folders and names accordingly of course and try it out...se if the error persists on your next boot [20:04] also...all virtualhosts can listen to *:443 [20:04]