[03:31] <hopeshare> hey community, I'm trying to use git with ubuntu server using ssh, I just installed git in my windows machine can someone help me in how to connect to my server using git and deploy my web just for testing purpose
[03:31] <hopeshare>  I have already created a key and configure it and it's working fine
[03:32] <hopeshare> I just need like a command in how to connect to the server using ssh key
[09:08] <sweb> i put my preseed.cnf to root of iso and make iso but seems be it's not loaded ... how can i sure my preseed file is loaded ? ubuntu 16.04 mini.iso
[12:34] <phantoms1> if im running nextcloud as an dockerimage is there a motive why I should stil whant to use as host OS server version (Ubuntu server) or can i use desctop
[12:47] <phantoms1> for hosting private server on the internet
[12:49] <thekrynn_> hello, was wondering if anyone might know why an NFS server I was running decided to stop working out of the blue (service nfs-kernel-server restart returns ok, but says nfsd not running)
[13:35] <sikun> phantoms1, have you used owncloud? if so what is the difference between that and nextcloud
[13:35] <sikun> ?
[13:37] <phantoms1> nextcloud is mor open … free the rely on customer support as income
[13:42] <sikun> ah
[13:42] <sikun> not like the enterprise as with owncloud
[14:22] <sweb> help me on this if you interest https://github.com/mhf-ir/ubuntu-overssh-reinstallation
[15:19] <ikonia> looks like a terrible idea and a very sloppy implementation
[16:20] <sweb> ikonia: try hetzner and stupid image installation to see what's the sloppy ... many datacenters use ubuntu-server-via-(extra package like plesk) as primary ubuntu iso installation .. no custom iso ... limited kvm for installation (time or cost) and much more limitation ... it's simple and fast way to clear installation ... what do you prefer ?
[16:20] <ikonia> I prefer not making bad install solutions like the one you're suggesting in the git repo
[16:26] <sweb> ikonia: i dont see any solution in `bad install solution` word ... give me a way ... give me solution to partition overssh without datacenter cooperation  ...
[16:26] <ikonia> don't do it
[16:26] <ikonia> thats the way to do it
[16:26] <sweb> ikonia: and explain me why
[16:26] <ikonia> because it's a bad install routing trying to do in situ, and the scripts in that repo are poor
[16:27] <ikonia> it also has uncceptable assumptions and dependencies
[16:29] <sweb> if script has problem community can fix it ... loading netboot over the grub imageboot is not good thinkg ? explain uncceptable subjects
[16:29] <ikonia> no
[16:30] <ikonia> the whole concept is not good
[16:30] <ikonia> talk to the DC to provide more realistic support options
[16:30] <ikonia> you're trying to engineer around a problem that shouldn't exist
[16:30] <ikonia> and if it does exist it's that element you need to fix, not an engineering solution
[16:33] <sweb> of course this is stupid problem ... but it exist ... we must deal with it ...
[16:34] <ikonia> no you shouldn't
[16:34] <ikonia> remove the proble
[16:34] <ikonia> problem
[19:05] <Sircle> how to enforce internet through squid and not anything else. If any thing has to be done on http/s via browser, wget, curl etc, it must go through squid or not at all. How to do that on ubuntu?
[19:20] <bekks> Sircle: Configure squid, and forbid direct connections to the internet using your firewall.
[19:21] <Sircle> bekks:  are you pointing to make iptable rules?
[19:22] <bekks> Sircle: Yes.
[19:22] <Sircle> bekks:  liek redirect all requests on port 80,8080,443 to go through squid? like this http://serverfault.com/a/445402?
[19:22] <bekks> Sircle: No.
[19:22] <bekks> "...  and forbid direct connections to the internet using your firewall"
[19:23] <bekks> Sircle: forbiding is not redirecting.
[19:24] <Sircle> bekks:  hm
[19:25] <Sircle> bekks:  so there is no way to automagically redirect 80,443 to squid (WITHOUT browser settings or any app settings). If so, this will cover wget and curl etc
[19:25] <bekks> Sircle: You are mixing things up.
[19:26] <bekks> If you want to REDIRECT, do it. If you want to FORBID, do it. But dont mix them up. :)
[19:26] <bekks> you said you want your squid to be used or if it isnt used, you want to forbid access. Thats not redirecting.
[19:27] <Sircle> ok, how to REDIRECT ALL 80,8080,443 port based calls to ssquid?
[19:28] <bekks> Sircle: like this: https://help.ubuntu.com/community/IptablesHowTo
[19:32] <Sircle> k
[19:34] <Sircle> step #1 allow squid to use 80,443 #2 redirect all other users' requests of 80,443 to squid 3128  bekks ?
[19:39] <bekks> No.
[19:39] <bekks> Sircle: Forbid direct internet access, not squid usage.
[19:40] <Sircle> bekks:  I do not want users to put proxy settings in browsers or apps everytime. Instead just redirect requests to squid. Its the same thing as blocking direct access
[19:40] <bekks> Sircle: Then still do not forbid usage.
[19:40] <bekks> And redirection is totally different from forbidding things.
[19:42] <Sircle> yes. I think redirection is better
[19:43] <Sircle> if suid is onn, it will take care. If its off, the request won't work either way