General Linux Chat and Small Questions v. I broke my Arch Install

[lavacano]

sftp root@your-hostname?

[vlad]

[QUOTE=lavacano;43300826]sftp root@your-hostname?[/QUOTE]

where do I put that in windows? :v: I use Bitvise SSH client for SFTP and SSH

[lavacano]

[QUOTE=PredGD;43300942]where do I put that in windows? :v: I use Bitvise SSH client for SFTP and SSH[/QUOTE]

I don't know those clients, but in FileZilla you'd enter sftp://your-hostname in the "host" box, root in the username box, and whatever your root password is in the password box

[vlad]

[QUOTE=lavacano;43301075]I don't know those clients, but in FileZilla you'd enter sftp://your-hostname in the "host" box, root in the username box, and whatever your root password is in the password box[/QUOTE]

didn't work sadly. tells me I'm using the wrong password even when I'm using the root password

[lavacano]

[QUOTE=PredGD;43301343]didn't work sadly. tells me I'm using the wrong password even when I'm using the root password[/QUOTE]

Can you SSH in as root?

If not, SSH in as normal user, and open /etc/ssh/sshd_config in a text editor (with sudo) - it should either be set up as "UsePAM yes" or "PermitRootLogin yes"

[vlad]

[QUOTE=lavacano;43301402]Can you SSH in as root?

If not, SSH in as normal user, and open /etc/ssh/sshd_config in a text editor (with sudo) - it should either be set up as "UsePAM yes" or "PermitRootLogin yes"[/QUOTE]

I can't log in as root, but I can easily log into the root account once I'm connected to the non-root account on the server

the settings in sshd_config are like they should be (UsePAM and PermitRootLogin)

[lavacano]

[QUOTE=PredGD;43301428]I can't log in as root, but I can easily log into the root account once I'm connected to the non-root account on the server

the settings in sshd_config are like they should be (UsePAM and PermitRootLogin)[/QUOTE]

Then I'm confused.

What distro are you running?

[vlad]

[QUOTE=lavacano;43301465]Then I'm confused.

What distro are you running?[/QUOTE]

arch

[shodan]

oh god my sides are exploding

You never used linux before
you decide to set up a vps for the first time
and the distro you pick is [b]FUCKING ARCH[/b]

Holy shit I need to lie down for a minute

[vlad]

[QUOTE=Mega1mpact;43303401]oh god my sides are exploding

You never used linux before
you decide to set up a vps for the first time
and the distro you pick is [b]FUCKING ARCH[/b]

Holy shit I need to lie down for a minute[/QUOTE]

never used linux before? I've used arch for the last half year or longer, and my linux experience begun around 3 years ago. what I'm new to is VPS, web hosting and servers in general.

where did you get that from? I'm pretty much a regular in this thread :v:

[shodan]

You just never pick arch for a vps. It's way too unstable for stuff like that.

Use good ol debian

[vlad]

it's more of a learning experience, nothing I'm gonna stick to so I feel that it shouldn't be that big of a problem to run it with arch. more comfortable with pacman, the aur, etc etc

[esalaka]

[QUOTE=PredGD;43303550]it's more of a learning experience, nothing I'm gonna stick to so I feel that it shouldn't be that big of a problem to run it with arch. more comfortable with pacman, the aur, etc etc[/QUOTE]

Yeah but Arch connected to the internet is one huge security vulnerability

[shodan]

I think awh is an arch user in denail

[ichiman94]

Why- How- What?

Arch has nothing to do with how secure the linux programs are, and doesn't force you to install updates every minute. It's as good as you build it. As for a server, you just install all the required things like apache and php, then you don't have to touch it for months. Why do you assume Arch is not good as a server distro, when everything a linux system depends on is its sys admin?

[Comfy]

Arch by design is not meant to be a distro suited for servers or anything related to productive PC's.

Bleeding edge packages for a server is just dumb. They can be unstable, and contain new security holes.

I usually either go with debian stable or centOS/RHEL on my servers.

[editline]26th December 2013[/editline]

And don't get me started on the update interval of arch... especially on a server.

[awh]

[QUOTE=kaukassus;43308727]Arch by design is not meant to be a distro suited for servers or anything related to productive PC's.

Bleeding edge packages for a server is just dumb. They can be unstable, and contain new security holes.

I usually either go with debian stable or centOS/RHEL on my servers.[/QUOTE]

New security holes are generally patched just as fast backported ones to other distros, though.
I run Arch on a couple of VPS', but I don't particularly care about them. I just like the familiarity and unsucky package management (yum might be ok, haven't tried it extensively).

[vlad]

I'm honestly not all that concerned about security issues at the moment. what is the worst that could happen? I don't store anything on there other than some test html's :v:

[editline]26th December 2013[/editline]

of course, after reading you guys replies, I'd most definitely switch to debian if I end up sticking to the server

[Doritos_Man]

[QUOTE=PredGD;43310412]I'm honestly not all that concerned about security issues at the moment. what is the worst that could happen? I don't store anything on there other than some test html's :v:

[editline]26th December 2013[/editline]

of course, after reading you guys replies, I'd most definitely switch to debian if I end up sticking to the server[/QUOTE]

Someone could gain access to your server to use it to host illegal items or use it for attacks.
You're liable for that.

[vlad]

[QUOTE=Doritos_Man;43310461]Someone could gain access to your server to use it to host illegal items or use it for attacks.
You're liable for that.[/QUOTE]

fair point, didn't think of that. what package manager does debian use? I've never used debian before (other than it's children, mint and ubuntu)

[editline]26th December 2013[/editline]

switched to debian and things are working well enough. can't get apache to look in /home/server/public_html even though I've pointed it to look there in /etc/apache2/mods-enabled/userdir.conf and enabled userdir. it's still looking in /var/www/ which I don't want it to

[lavacano]

Different distros do their configs differently, so I'm not sure where Debian keeps the specific file, but you should set the default vhost's serverroot to that directory

[vlad]

yeah I made sure to follow the debian wiki but it's really lacking I feel. I did what it told me to do when configuring user directories. tried looking for the vhost thing you mentioned but couldn't find it in any of the config files where I feel it makes sense to have it in

[editline]26th December 2013[/editline]

does this really fit in this thread anymore? I mean, it's linux and all, but noticed that the web development forum has a questions thread so wondering if my posts are more relevant there?

[lavacano]

You could try WebDev but I think their questions thread more geared toward the stuff that actually goes on the server

In Gentoo the file is /etc/apache2/vhosts.d/00-default-vhost.conf (the 00 might be different, I don't have an install in front of me currently).

[vlad]

yeah I don't have folder in /etc/apache2 sadly

is there something I'm doing wrong maybe?
[url]https://wiki.debian.org/LaMp#apache2[/url]
I followed that to the letter

[lavacano]

according to that wiki article, they just do /etc/apache2/apache2.conf

should be in there somewhere then

[vlad]

just skimmed through the entire config file and found nothing.

[url]http://tny.cz/c7797717[/url]

this is apache2.conf, in case you want to skim through

[nikomo]

If you're trying to conf a vhost in Apache2 under Debian, check /etc/apache/sites-available/
You can throw shit in the default file, or make a new file, symlink it to sites-enabled and restart Apache.

[vlad]

heyyy, thanks nikomo! found all the things I was looking for in that. that folder was honestly the last place I would've thought of these being

[nikomo]

I've been using Debian-based distros for the last 5-6+ years, it's the only place where I could think to look nowadays.

[shodan]

[QUOTE=nikomo;43311922]If you're trying to conf a vhost in Apache2 under Debian, check /etc/apache/sites-available/
You can throw shit in the default file, or make a new file, symlink it to sites-enabled and restart Apache.[/QUOTE]
the 2nd thing nikomo said is the best way. It's a lot more organised

Also it might be smart to make www folder in /srv and make a folder for every site.
My structure is like this:

/srv
└── www
    ├── Antarctica.BasBieling.com
    │   ├── logs
    │   └── public_html
    ├── el.BasBieling.com
    │   ├── logs
    │   └── public_html
    ├── School.BasBieling.com
    │   ├── logs
    │   └── public_html
    ├── www.BasBieling.com
    │   ├── logs
    │   └── public_html
  {...}

I can post some config files for sites that have php enabled etc if you want