[05:21] <cpaelzer> good morning
[06:07] <lordievader> Good morning
[06:07] <cpaelzer> hi lordievader
[06:08] <lordievader> Hey cpaelzer How are you doing?
[06:09] <cpaelzer> lordievader: fighting my inbox after PTO before it steals my soul :-) so I'd say good
[06:09] <cpaelzer> lordievader: and you?
[06:12] <lordievader> Doing good here
[07:10] <cyrils34> Hello All
[07:14] <cyrils34> I'm new on ubuntu server. I have ha dedicated hosting on Go daddy with Ubuntu server 16.04 (no control pannel)  and i get some trouble for configure my dns and ssl. Did someone can help me ?
[07:15] <tomreyn> cyrils34: hi, please discuss these issues in detail.
[07:18] <tomreyn> just to understand where you're coming from: you say you previously had 'dedicated hosting', so this was a dedicated server / VM, managed by Godaddy (but you probably had a login, just not root access)?
[07:19] <cyrils34> on go daddy website i get nothing for manage the server, i get only a button for restart it, else everything is made by ssh
[07:19] <cyrils34> and i have root access
[07:20] <tomreyn> ok, so effectively ouy already managed an ubuntu server before.
[07:21] <cyrils34> I have follow some tutorial for configure the dns and ssl, but seems i've make some mistake, when i write my domain name on browser www.exemple.com, i get back my ip and not the www.exemple.com and ssl i get NET::ERR_CERT_COMMON_NAME_INVALID
[07:23] <tomreyn> i will continue to subsitute www.exemple.com for your actual domain name, which i do not need to know for now.
[07:25] <tomreyn> i will substitue 1.2.3.4 as the ip address www.exemple.com resolves to (as a result of running 'host www.exemple.com')
[07:25] <cyrils34> ok
[07:26] <tomreyn> you say "when i write my domain name on browser www.exemple.com, i get back my ip and not the www.exemple.com". does this mean that when you access http://www.exemple.com, does it redirects you to http://1.2.3.4 and your web browser shows this address in the address bar in the end?
[07:27] <cyrils34> yes
[07:27] <tomreyn> so it really shows your servers' ip address in the web browsers' URL bar in the end, are you sure? this is an unusual misconfiguration, if so.
[07:29] <cyrils34> yes, i write www.exemple.com and on chrome i get 1.2.3.4
[07:29] <tomreyn> so the address hown in the address bar actually updates to the ip address of the server, ok.
[07:30] <cyrils34> yes
[07:30] <tomreyn> do you have another linux computer where oyu can run some commands on?
[07:31] <cyrils34> i have install ubuntu server 16.04 on my laptop for make some try, so yes i have
[07:32] <tomreyn> so when you run "host www.exemple.com" on your laptop's ubuntu, does it say "host www.exemple.com has address 1.2.3.4"? does it say something else?
[07:32] <tomreyn> anything about "CNAME" or "alias"?
[07:34] <cyrils34> its show me an ip but not my hosting server . If i copy this ip to chrome, is open godaddy website where is a page for make a long url to short url
[07:35] <tomreyn> ok, now try this (similar but not the same):
[07:35] <tomreyn> so when you run "host exemple.com" on your laptop's ubuntu, does it say "host exemple.com has address 1.2.3.4"? does it say something else?
[07:36] <cyrils34> also say exemple.com mail is handled by 0 mywebsite.com.mail.protection.outlook.com
[07:37] <tomreyn> okay, is this wrong?
[07:37] <cyrils34> no this is right
[07:37] <tomreyn> and it DOES say "host exemple.com has address 1.2.3.4", right?
[07:37] <cyrils34> yes
[07:38] <cyrils34> but is not my address as what i said before, is give an ip and if i go on this ip is going to shortener.godaddy.com
[07:38] <tomreyn> okay, so what you need to do is to update authoritative DNS for your domain name.
[07:38] <tomreyn> oh there, too, ok
[07:40] <cyrils34> ok, how to do ?
[07:40] <tomreyn> this authiritative DNS service is usually run by the comapany where you rent your domain name.
[07:40] <tomreyn> *authoritative
[07:41] <cyrils34> i have buy the domain on godaddy only, then after x months i have buy a dedicated server on godaddy
[07:41] <tomreyn> what you need to make sure is that both www.exemple.com and exemple.com point to 1.2.3.4 there.
[07:42] <tomreyn> i am not a godaddy customer and can't guide you to their web panels for domain management.
[07:42] <tomreyn> but they surely have some form of customer support for this.
[07:43] <cyrils34> i will tell you what i have wait a little
[07:45] <tomreyn> also, none of this has anything to do with ubuntu really (it is not specific to the operating system you run on your server), it's just about the basic workings of how hostnames are resolved to ip addresses on the internet. you should normally talk to godaddy for getting help with this.
[07:47] <cyrils34> i have think my problem was with bind
[07:49] <tomreyn> so you run a nameserver on your server. does it serve as the authoritative name server for your domain name? maybe you want to point us to the tutorial you have been following.
[07:51] <cyrils34> the tutorial is a video in french, but i can copy to you the code i've write on the file of bind
[07:52] <tomreyn> !paste | cyrils34
[07:53] <tomreyn> (also, i could probably still understand at least the technical information on a french tutorial.)
[08:01] <cyrils34> https://imgur.com/a/k0h3vdj
[08:01] <cyrils34> https://imgur.com/a/sSVdv1s
[08:01] <cyrils34> https://imgur.com/a/bRIjFcM
[08:02] <cyrils34> that's the 3 files i've edit
[08:07] <blackflow> cyrils34: can you pastebin them please?
[08:07] <blackflow> and it'd be great if you didn't obfuscate anything so we can check what resolves where and how.
[08:13] <cyrils34> ok wait
[08:14] <cyrils34> and just for know, did i get an ssl error because the dns or the 2 problems are different ?
[08:15] <blackflow> cyrils34: they're unrelated, the ssl error is about expired or invalid name certificate (you access example.com by https, and the cert is for anotherdomain.com)
[08:22] <tomreyn> cyrils34: your SAO record, as seen on https://imgur.com/a/bRIjFcM , is most likely incorrect
[08:22] <tomreyn> *SOA
[08:23] <cyrils34> ah ?
[08:24] <tomreyn> it says ksXXXXXXXXX...
[08:24] <blackflow> I understood those are screens from the tutorial, not actual config files?
[08:24] <tomreyn> oh, that's possible
[08:24] <cyrils34> yes, im copying what i have change
[08:25] <cyrils34> screenshot is tutorial
[08:25] <blackflow> so please pastebin the actual configs you have?
[08:25] <cyrils34> yes wait im doing
[08:38] <tomreyn> you're not. ;)
[08:39] <cyrils34> almost done
[08:39] <blackflow> cyrils34: are you.... typing it out? O.o
[08:47] <cyrils34> https://paste.ubuntu.com/p/2vvnqTxhRG/
[08:48] <cyrils34> https://paste.ubuntu.com/p/JSK8cnncBQ/
[08:49] <cyrils34> https://paste.ubuntu.com/p/tTHjqgHdvd/
[08:52] <blackflow> cyrils34: you seem to have a different NS entry there. I'm guessing domaincontrol.com is not yours :)
[08:52] <blackflow> cyrils34: so what are the NS entries on the domain at your registrar? that's why I asked you did NOT obfuscate data, so we can check the entire chain.
[08:53] <cyrils34> the only thing i change is mywebsite.com and change number of ip by XXX
[08:53] <cyrils34> all other is what i get
[08:53] <cyrils34> in godaddy is write domaincontrol
[08:55] <blackflow> cyrils34: your zone is wrong then
[08:57] <cyrils34> ah ?
[08:58] <blackflow> cyrils34: yes. when your domain name is resolved, your registrar points to IPs in the NS entries. Which NS entries are there? the server you run Bind on, or domaincontrol.com?
[08:58] <lordievader> Brr, wildcard record
[08:59] <blackflow> whoever is listed there, is authoritative for your domain. so either you do NOT have control with that Bind, or you do but your NS entry is wrong.
[09:00] <lordievader> What is the actual domain  name cyrils34 is trying to configure?
[09:01] <blackflow> cyrils34: also line 11 in the second pastebin does not look correct. That quote looks invalid. Should be  zone "mywebsite.come" { ...; };
[09:02] <blackflow> lordievader: well I asked them NOT to obfuscate so I can check it, but no answer to that.
[09:02] <lordievader> cyrils34: What domain are you trying to configure?
[09:11] <cyrils34> hmmm im not sure to understand
[09:11] <cyrils34> did you mean that i need not to configure bind because godaddy do it already ?
[09:13] <blackflow> cyrils34: if you want any more help from me (and others here I assume) you will have to start telling which domain it is so we can check. Also you did not answer my question about NS entry at the registrar.
[09:13] <blackflow> cyrils34: also consider NOT running a public server that can harm others on the internet, ESPECIALLY not a DNS server which can harm others VERY much if you don't know the basics of DNS.
[09:15] <lordievader> Good point. Do make sure to disable recursion.
[09:15] <lordievader> We have enough open resolvers on the internet 😉
[09:16] <blackflow> it's fun when you combine that with a cheap godaddy 1gbps piped "servers for masses" and turn it into a 1gbps udp gun for hire....
[14:55] <ahasenack> rbasak: how do you usually verify Dropped changes from a delta, in a merge MP? Compare the new (logical) delta with the old one?
[15:00] <rbasak> ahasenack: yes. I run "git log -p --reverse old/debian..logical/..." in a left window and "git log -p --reverse new/debian..merge-branch" in a right window.
[15:00] <rbasak> Then for every commit on the left, I should see it mentioned in the new changelog and accordingly dropped, transferred or modified.
[15:02] <ahasenack> ok
[15:02] <ahasenack> let me try that
[15:11] <rbasak> cpaelzer: bug 1487679 came up in my 180 day warning. IMHO, it's not critical. It's a relatively uncommon use case and one where users can be expected to tweak /etc as they need anyway. What do you think we should do about it? Just take it off our backlog? Anything else?
[15:13] <blackflow> yuck!
[15:15] <easyOnMe> hello everyone
[15:15] <easyOnMe> just want to ask
[15:16] <easyOnMe> what is the terminal command to implement all the config files in the sites-available folder to the sites-enabled folder
[15:17] <easyOnMe> I only have one file containing all the vhosts directives with one main domain and the rest are all subdomain directives
[15:17] <easyOnMe> please help
[15:18] <cpaelzer> rbasak: yeah I think it is loosing the high-effort-VS-rare-case
[15:18] <cpaelzer> rbasak: I'd be ok to remove it, but OTOH it is a valid case so you might add the bot-stop-nagging tag instead
[15:19] <cpaelzer> if you think we would get to it one day
[15:19] <cpaelzer> if not, lets be honest and state that we likely don't get to it
[15:20] <blackflow> easyOnMe: I don't know apache tools (and I'm guessing it's apache from your question in #ubuntu), but those should all be symlinks, yes? if so, you can just symlink them manually
[15:24] <easyOnMe> blackflow: how do I do that
[15:28] <blackflow> easyOnMe: check the ln manpage  (man ln)  . something along the lines of        ln -s /etc/.../sites-available/foo.bar /etc/.../sites-enabled/foo.bar       -- I don't know exact paths or filenames involved, for each vhost in sites-available that you want to make enabled.
[15:36] <easyOnMe> blackflow: thanks man
[15:36] <Ussat> So, is the upgrade from 16.04 --> 18.04LTS avaliable at the moment ?
[15:37] <Ussat> I would like to fun some tests with my test boxes
[15:37] <Ussat> s/fun/run/
[15:38] <blackflow> easyOnMe: so if there's more of them, maybe an onliner like this (make sure you understand what this does first):    cd /etc/.../sites-available/ ; for F in * ; do [ ! -L "../sites-enabled/$F" ] && ln -s "$F" "../sites-enabled/$F" ; done
[15:39] <easyOnMe> blackflow: I did the first one but it says the file exists already
[15:39] <easyOnMe> now I am tempted to copy the file from sites-available to sites-enabled
[15:40] <blackflow> easyOnMe: no, the whole point of sites-available and sites-enabled is symlinking
[15:40] <easyOnMe> exactly but the first command did not succeed
[15:41] <blackflow> easyOnMe: but the file is already there you say, linked?
[15:41] <easyOnMe> blackflow: what i mean is update the one in the sites-enabled
[15:41] <easyOnMe> I did changes in the files in sites-available and they are not update in the sites-enabled
[15:42] <blackflow> easyOnMe: I don't know what you're doing there.  your config _files_ should be in sites-available.   you then _symlink_ those you want active into sites-enabled. the point of symlinks is that you don't end up with TWO copies of the file
[15:42] <easyOnMe> the sites-enabled files are still the old versions
[15:42] <blackflow> and from what I understand, the tools that manage those, expect and require symlinks.
[15:42] <easyOnMe> blackflow: I really do not know man
[15:42] <easyOnMe> probably i messed it up
[15:42] <easyOnMe> now I am trying to figure out how to correct what I messed up
[15:43] <easyOnMe> any ideas?
[15:43] <blackflow> well I just told you what you should have. if you have files in sites-enabled, instead of symlinks to their counterparts in sites-available, you should fix that first.
[15:44] <blackflow> easyOnMe: btw, this sites-enabled/sites-available paradigm is specific do debian (and derivatives, like Ubuntu)  configuration of apache. it is _not_ mandatory by Apache
[15:44] <blackflow> *to
[15:45] <easyOnMe> blackflow: I see
[15:45] <easyOnMe> but my subdomains are not working
[15:45] <easyOnMe> all the subdomains keepon saying the error:
[15:45] <blackflow> which means I'm assuming you're using the default config templates. which means the main apache config file should source from the sites-enabled (not sites-available!) directory for vhost configs.
[15:45] <easyOnMe> blackflow: erver certificate does NOT include an ID which matches the server name
[15:45] <easyOnMe> *server
[15:46] <easyOnMe> until now I not resolve this issue
[15:46] <easyOnMe> I am past my dinner time already
[15:46] <blackflow> that's a bit beyond being ubuntu specific and should perhaps ask for help in #apache, on how to configure and use the Apache web server.
[15:46] <blackflow> easyOnMe: is that a public server btw?
[15:46] <easyOnMe> blackflow: what do you mean public
[15:46] <easyOnMe> you mean online already
[15:47] <blackflow> hosting sites or services available on the public internet
[15:47] <easyOnMe> yes
[15:47] <blackflow> eg. not in your LAN
[15:47] <easyOnMe> no
[15:48] <blackflow> right. so consider NOT doing that until you've learned how to manage Apache properly. Doing this and not knowing what you're doing, on public internet, can HARM others.
[15:58] <npgm> I did a netinstall of 18.04 and got everything up and running very well. Realized I need 16.04 though, so made a netinstall usb with that and went to install. First issue: very slow install during the "preparing $package" phase.
[15:58] <npgm>  Second issue: upon reboot I was dropped directly into an EFI shell. Tried following these instructions, no luck: https://askubuntu.com/questions/597213/bootable-device-not-found-after-clean-install-of-ubuntu-14-04-uefi
[15:59] <npgm> Now, I try to boot from the install media again, and the display never comes up, I can switch to a separate TTY though, whats the default login creds for a netinstall iso?
[15:59] <Ussat> easyOnMe, I would take that down untill you have it configured correctly
[15:59] <Ussat> Just my opinion
[16:02] <easyOnMe> Ussat: I see
[16:02] <easyOnMe> it is only the subdomain that is not working well
[16:02] <easyOnMe> the main domain is ok
[16:02] <easyOnMe> and the subdomains are not yet open for use
[16:02] <easyOnMe> it is just for testing only
[16:02] <Ussat> Then I would test on a non live server
[16:02] <Ussat> testing in prod is...not the best idea IMHO
[16:03] <easyOnMe> I manage to achieve success in my local server but in the public server I just could not figure out what I missed doing correctly
[16:05] <blackflow> easyOnMe: perhaps then start with actual problem you're having? Like, you're doing X, and expect Y to happen but instead, Z happens.
[16:05] <easyOnMe> blackflow: that is what I am doing
[16:05] <easyOnMe> witht he subdomain
[16:05] <easyOnMe> but I cannot figure out how to resolve the errors I am encountering especially the one I just shared
[16:06] <easyOnMe> that is the only one left to solve and I am good to go
[16:06] <blackflow> easyOnMe: no, I mean explain here what you have and what you're trying to achieve.
[16:06] <easyOnMe> easyOnMe: oh I see
[16:07] <blackflow> for example, pastebin the errors you're encountering.
[16:07] <easyOnMe> I wanted establish a subdomain and like subdomain1.example.org and expect it to show up on the browser when I hit enter
[16:08] <easyOnMe> unfortunately it says:This page isn’t working
[16:08] <easyOnMe> sg.infinityls.org redirected you too many times.
[16:08] <blackflow> easyOnMe: first of all, is the DNS for it valid and resolving to correct IP?
[16:08] <easyOnMe> blackflow: yes
[16:08] <easyOnMe> https://apaste.info/8D3R
[16:08] <easyOnMe> just ignore the output for the back up file
[16:08] <easyOnMe> it has been deleted already from the sites-enabled folder
[16:09] <blackflow> easyOnMe: yeah and don't put files into sites-enabled
[16:10] <blackflow> so, can you pastebin the actual vhost file you're using?
[16:10] <easyOnMe> blackflow: I don't but for some reason the back up came out when I did apachectl -S
[16:10] <easyOnMe> the back up became part of the output
[16:10] <easyOnMe> I also do not know why it became included in the sites-enabled
[16:10] <blackflow> probably syslog with crit(ical) level which is configured to go to console
[16:11] <blackflow> wait, that is actually the contents of the file?
[16:18] <Ussat> looks like a serious miss-paste
[16:19] <easyOnMe> blackflow: virtual host config for the main domain and the subdomains
[16:19] <easyOnMe> for port 443
[16:19] <easyOnMe> and port 80
[16:20] <blackflow> easyOnMe: yes, but is that.... no, wait. can you pastebin the _actual_ file?       cat /etc/.../sites-enabled/foo.vhost.conf | nc termbin.com 9999     and post here the URL you get       of course use proper path.
[16:21] <easyOnMe> blackflow: its the same
[16:21] <easyOnMe> i just changed the names of the subdomain and the main domain
[16:21] <easyOnMe> basically what you see there that is it
[16:22] <blackflow> that is not a correct apache config file syntax
[16:27] <blackflow> easyOnMe: looks like you copypasted some output of grep or something.
[16:30] <easyOnMe> blackflow: no that is the result of apachectl -S
[16:30] <blackflow> easyOnMe: so why don't you pastebin the actual file
[16:31] <easyOnMe> blackflow: because our work does not allow us to
[16:31] <easyOnMe> we seek help but we are not allowed to pastebin actually files with real names
[16:31] <blackflow> easyOnMe: then how do you expect anyone to help you?
[16:31] <easyOnMe> so I changed it to subdomain and maindomain
[16:31] <easyOnMe> so I do not get fired
[16:31] <blackflow> I can't help you untill I see what your config is and what's wrong with it.
[16:32] <easyOnMe> I see
[16:32] <easyOnMe> but that is the best I can do man
[16:32] <blackflow> btw.... this is not Ubuntu specific, so please direct all your Apache support request to #apache.
[16:32] <easyOnMe> the mainDomain is the dns name
[16:32] <blackflow> over and out.
[16:32] <easyOnMe> subdomain are the respective subdomain names
[16:32] <easyOnMe> ok no problem
[16:33] <easyOnMe> thanks for the attention though
[16:33] <Ussat> So, is the upgrade from 16.04 --> 18.04LTS avaliable at the moment ?
[16:33] <teward> Ussat: not until the 18.04.1 release
[16:33] <Ussat> ahh...gotcha, thanks
[16:33] <teward> yep.
[16:34] <blackflow> easyOnMe: I do have to ask what kind of work is that where you're not fired and are supposed to touch production machines with zero clue. all this smells like BS to me.
[16:34] <easyOnMe> blackflow: it is just the names that are changed man I do not think it really matters that much
[16:35] <Ussat> Yes, yes it does
[16:35] <easyOnMe> how so
[16:35] <blackflow> easyOnMe: when you have no clue how to configure apache, and are asking for help, don't assume you know what is or isn't relevant.
[16:35] <easyOnMe> just following protocol here man
[16:36] <easyOnMe> anyone its ok
[16:36] <easyOnMe> sorry if it offends you
[16:36] <easyOnMe> this is my first job
[16:36] <easyOnMe> *anyway
[16:36] <blackflow> I just don't buy it any more that you have a legit help request.
[16:36] <easyOnMe> blackflow: I really do
[16:36] <easyOnMe> the other day I got a good dressing down for similar case
[16:37] <easyOnMe> so just learned some lessons too
[16:37] <easyOnMe> anyway man its ok
[16:37] <Ussat> I assume you have backups ?
[16:37] <easyOnMe> yes we do
[16:37] <blackflow> well if you're serious, I'd gtfo of there asap and find a better job, one that offers proper training and supervision, before allowing anyone to prod.
[16:37] <easyOnMe> blackflow: I do but I am newbiew who will hire me with no experience at all
[16:38] <Ussat> restore latest working GOOD backup, and test in test
[16:38] <easyOnMe> Ussat: ok will do
[16:38] <easyOnMe> thanks
[16:38] <Ussat> Thats MY opinion
[16:38] <easyOnMe> Ussat: I will take it from there though
[16:38] <Ussat> and dont touch prod till you are 100% sure
[16:38] <easyOnMe> Ussat: no problem
[16:41] <blackflow> easyOnMe: but seriously, find another, more responsible company, before they dump on you the next Equihax and hang you out to dry.
[16:41] <easyOnMe> blackflow: yeah in our country here I consider myself lucky man
[16:41] <easyOnMe> a lot of people here have no work or job to speak of
[16:42] <easyOnMe> for me with no experience having this job this is already a blessing to start with
[16:42] <easyOnMe> difficult yes, but that is where all newbies start anyway
[16:42] <easyOnMe> one year max and I am out of this company
[16:43] <easyOnMe> this company is not that big too so they kind of hire people whom they can make the most out of
[16:43] <easyOnMe> blackflow: anyway thanks dude for the advice
[16:43] <easyOnMe> really appreciate all your help earlier
[16:43] <blackflow> easyOnMe: the problem is not in not having experience. nobody was born with it. the problem is all the rest about it. esp. the cherry on top, of being unable to pastebin a config file, even with obfuscated domains.
[16:44] <easyOnMe> blackflow: that was the actually config file already
[16:44] <blackflow> that is not a valid apache config file, so no :)
[16:44] <easyOnMe> the name of the file is 000-default-le-ssl.conf
[16:44] <blackflow> easyOnMe: these are:  https://httpd.apache.org/docs/2.4/vhosts/examples.html
[16:45] <easyOnMe> I got it from the /etc/apache2/sites-available folder
[16:45] <blackflow> ServerRoot: "/etc/apache2"  is not a valid apache config stanza
[16:45] <easyOnMe> blackflow: oh so sorry I got what you mean
[16:45] <easyOnMe> man I am very sorry
[16:45] <easyOnMe> I assume I pastebin the 000-default-le-ssl.conf
[16:46] <easyOnMe> blackflow: man really sorry my bad
[16:46] <easyOnMe> hang on
[16:46] <blackflow> that still wouldn't look like a valid config file. apache config syntax doesn't have   keyword: value    stanzas
[16:47] <easyOnMe> blackflow: yeah I agree so sorry man
[16:48] <easyOnMe> brb
[16:48] <blackflow> np
[16:48] <easyOnMe> not to restart this laptop
[16:48] <easyOnMe> hang on
[17:02] <easyOnMe> blackflow: here it is man: https://apaste.info/Bm9W
[17:02] <easyOnMe> thanks for the wait
[17:06] <blackflow> easyOnMe: I don't see a redirect rule there that could explain that previous error. Did you try cleaning your browser cache? If there was a 301 there somewhere before, it could've been cached in your browser. Also, is there PHP involved that could explain any redirections happening that aren't visible in vhost configs?
[17:06] <easyOnMe> blackflow: yes there is some php involve
[17:06] <blackflow> and see, if you didn't obfuscate the domain name, now someone could try to connect and see the headers and progression of redirects...
[17:06] <easyOnMe> i am using .htaccess too
[17:07] <blackflow> oh .htaccess, check that too, it's config too
[17:07] <easyOnMe> blackflow: are you familiar with codeigniter3
[17:07] <blackflow> ten years ago I was.
[17:08] <easyOnMe> blackflow: I am using it now and what I did was just to copy the application and system folders inside each subdomain folder
[17:08] <easyOnMe> now to test one subdomain I tried performing the necessary config adjustments but to no avail
[17:09] <easyOnMe> but when I did with my local server I got it running very well
[17:09] <easyOnMe> blackflow: now I did apachectl -S and the error there states that there is no id matching the server name
[17:10] <easyOnMe> so I came to the conclusion that the multiple redirect was the result of the failure to match the cert id with the correct server name
[17:11] <blackflow> easyOnMe: can you pastebin    culr -v -s http://<your domain here> 1>/dev/null      run from a linux machine with curl installed, use proper subdomain, one that results in inifinite redirects
[17:12] <blackflow> easyOnMe: no, SSL certs don't result in http redirects in any way.
[17:12] <blackflow> btw, I typoed up here, it's curl   not    culr
[17:12] <easyOnMe> blackflow: ok noted with thanks
[17:13] <easyOnMe> blackflow: shall i use https instead of http
[17:13] <blackflow> no, use http
[17:13] <easyOnMe> ok
[17:13] <blackflow> actually do both.   properly configured SSL should have a redirect from http to https anyway
[17:14] <easyOnMe> blackflow: do I include the number 1 here:<your domain here> 1>
[17:15] <Ussat> ya.....we just changed all our internal stuff to be https a,d http redirects to https
[17:15] <Ussat> well, over the last month
[17:15] <blackflow> easyOnMe: yes,   1>/dev/null is a separate param, redirects stdout to devnull.    in fact 1 is not needed,   >/dev/null shold work, but I like to be explicit about those
[17:15] <Ussat> we have an internal CA for the internal stuff
[17:15] <easyOnMe> blackflow: ok
[17:16] <blackflow> easyOnMe: because curl will output the fetched site content to stdout, and we don't need that here, only hte headers (with -v) that are output to stderr
[17:20] <easyOnMe> blackflow: https://apaste.info/trtB
[17:20] <easyOnMe> that is the result
[17:21] <easyOnMe> same for the other subdomains
[17:22] <blackflow> easyOnMe: okay that's a 302 to https. now please do https
[17:22] <easyOnMe> blackflow: that is https
[17:22] <easyOnMe> please see line 1
[17:23] <blackflow> oh right... well that's the problem there, you have a redirect back to itself.
[17:23] <easyOnMe> blackflow: hang one
[17:23] <easyOnMe> for the other subdomains its 402
[17:23] <blackflow> HTTP/1.1 302 Found    and Location: https://subdomain6.example.org/
[17:23] <blackflow> easyOnMe: please pastebin the file   /etc/letsencrypt/options-ssl-apache.conf
[17:23] <easyOnMe> blackflow: for the other subdomains its 403 sorry
[17:24] <easyOnMe> blackflow: ok hang on
[17:24] <blackflow> 403 is okay, means you don't have a permission to view it, but it's not a broken redirect back to itself.
[17:26] <easyOnMe> blackflow: https://apaste.info/9hVm
[17:27] <blackflow> easyOnMe: huh, okay, so what about .htaccess files. Any redirect rules there?   RewriteRule   directoves?
[17:27] <easyOnMe> blackflow: yeah but when I started configuring subdomain6 this issue occurred initially subdomain6 was also 403 error
[17:27] <blackflow> *directives
[17:27] <easyOnMe> blackflow: ok I will pastebin it too
[17:29] <easyOnMe> blackflow: https://apaste.info/2lej
[17:30] <easyOnMe> that is the .htaccess for subdomain6
[17:30] <easyOnMe> which is very similar to the its mainDomain's htaccess
[17:30] <blackflow> and that's it, lines 5 and 6
[17:30] <easyOnMe> blackflow: why what about those lines
[17:30] <blackflow> line 5 should have 80 and not 443 in the RewriteCond
[17:30] <easyOnMe> ok
[17:31] <easyOnMe> what about line 6
[17:32] <blackflow> line 6 looks good if the idea is to redirect http to https and retain the URI
[17:32] <easyOnMe> blackflow: so only line 5 change back to 80
[17:32] <blackflow> I'm not sure about the RewriteBase, I'm a bit rusty in Apache....
[17:32] <easyOnMe> i see
[17:32] <easyOnMe> never mind let's see
[17:34] <blackflow> btw, why is that in .htaccess.... ideally you should not have any .htaccess files. that is useful only for shared hosting environments when you want to allow users change httpd configs without touching the master config file
[17:35] <easyOnMe> blackflow: that's what I learn
[17:35] <easyOnMe> since I learned using codeigniter
[17:35] <easyOnMe> blackflow: by the way we are back to 403 error
[17:35] <blackflow> well at least the cycling redir is fixed :)
[17:35] <easyOnMe> now the issue is that it does not use codeigniter's own index file
[17:35] <blackflow> there should be apache error log somewhere, check in there what is it failng on
[17:36] <easyOnMe> ok hang on
[17:37] <blackflow> you need DirectoryIndex index.php   to tell apache to automatically assume index.php to be the index file, when one is not given
[17:37] <blackflow> see, when you access http://domain.org/   you're technically acessing  /index.html, implicit through DirectoryIndex directive
[17:38] <easyOnMe> blackflow: yes correct I agree in fact 403 will not pop out if index.html is around
[17:39] <easyOnMe> the thing is the folders for ci such as applications and system are already inside the subdomain6 folder so by right it should look for the controller file right
[17:39] <blackflow> and that's a whole new level of problems. configuring PHP for apache. I can't help you there, it's really been a while since I apache'd.   Best ask in #apache.
[17:39] <easyOnMe> but it this case it did not
[17:39] <easyOnMe> instead it tried to look for index.html instead of the main controller
[17:40] <easyOnMe> blackflow: yeah I went in there but the guys there seem clueless or probably asleep
[17:40] <easyOnMe> lol
[17:40] <blackflow> Try adding DirectoryIndex index.php   to that .htacccess
[17:41] <blackflow> oh wait.... you have Options -Indexes in the main vhost files.... try removing that too
[18:10] <seizo> im trying to install ubuntu 18.04 server on an apu2c4 board, need to force it to use serial interface instead of gfx. how can i make changes to the install iso?
[18:29] <RoyK> seizo: not sure, but something like console=serial(something) in the kernel line might do the job
[18:30] <RoyK> seizo: hm - it's not the console that's the problem - it's TTYs - not sure how to enable serial TTYs during instaall
[18:38] <oerheks> maybe a help https://help.ubuntu.com/community/SerialConsoleHowto
[18:55] <seizo> RoyK: yeah thats what im thinking, trying to figure out how to edit the grub file on the read-only iso / live usb stick
[18:56] <seizo> oerheks: yeah i found that, most of the info is way out of date :/
[19:03] <npgm> I'm having some issues with a USB 3.0 ethernet adapter. The driver seems to be a bit buggy from what I can tell (kevent 12 error msgs). I'm running a fresh 16.04 install. Basically I need a USB NIC thats as reliable and plug and play as possible, the actual speed doesn't matter so much. Does anyone have a recommendation on something to pick.
[19:14] <sarnold> npgm: I'd try 18.04 before giving up on the thing
[19:14] <npgm> sarnold: ya, so given my use case its more cost effective for me to pick something that works, this is for a largescale deployment
[19:15] <npgm> if theres some usb 2.0 NIC thats known to have a mature reliable driver on 16.04 thats much better for me
[19:15] <sarnold> npgm: ah. then *maybe* the 16.04 LTS HWE stack would be a nice medium.
[19:17] <npgm> sarnold: ya, thats not an option as well. :D sorry for all the constraints.
[19:17] <npgm> is there some place I can look to find a list of _very_ well supported hardware?
[19:17] <sarnold> npgm: heh, bummer :)
[20:32] <Mystic_Reverie> any other ubuntu helps rooms anywhere?  the 'ubuntu'  people are such aloof snobs, im stuc kwith ubuntu and i dread going in there asking for help now.
[20:34] <_KaszpiR_> Mystic_Reverie dont' expect better support, really
[20:35] <Mystic_Reverie> ive had great support in here, when they are around
[20:35] <nacc> Mystic_Reverie: also pleaes don't corosspost
[20:35] <nacc> *crosspost
[20:35] <nacc> Mystic_Reverie: your question has nothing to do with ubuntu server
[20:35] <nacc> Mystic_Reverie: you just didn't like the answer in #ubuntu
[20:35] <Mystic_Reverie> oh sorry wrong room.  im not corss posting , am asking fo a room that isnt full of nasty snobs
[20:35] <Mystic_Reverie> im fine in other rooms, puppy linux ect
[20:35] <Mystic_Reverie> some people in ubuntu had a nasty attitude problem
[20:35] <nacc> Mystic_Reverie: that's not the purpose of this channel
[20:35] <nacc> !alis | Mystic_Reverie
[20:36] <hggdh> Mystic_Reverie: please don't go there
[20:36] <Mystic_Reverie> get stuffed
[20:36] <Mystic_Reverie> u need to learn hpw t otreat people
[20:37] <nacc> lol
[21:52] <Ragz> Hi all
[21:53] <Ragz> anyone help with server migration from 12.04 to 14.04?
[21:55] <nacc> Ragz: 12.04 has been eol for a while
[21:55] <nacc> !eolupgrade | Ragz
[21:55] <nacc> Ragz: you are better off reinstalling
[21:56] <nacc> (IMO)
[21:57] <Ragz> Thanks guys, only issue is i got word press sitting on it
[21:57] <Ragz> and i dont have enough word press experience
[21:58] <Ragz> tried migrating the dam thing but kept on failing due to one of it plugins which no one supports
[21:58] <Ragz> spent most of the day trying to upgrade from 12.04 to 14.04 but mysql doesnt want to start
[21:58] <Ragz> or apache breaks
[23:01] <JanC> probably better drop that extension if you can then...
[23:02] <JanC> or plugin or whatever it's called
[23:02] <JanC> maybe replace it if possible...
[23:02] <JanC> and do that before trying to upgrade...
[23:06] <sarnold> JanC: ragz's been gone for a while :(
[23:07] <JanC> I know
[23:07] <JanC> maybe he/she will come back  :)