help,I mess my vps [again]

MeMyselfandLinux

Hello,its me,the n00b (again)

Recently i install my vps with tiger's script

https://github.com/TigersWay/VPS

removing the part

IPS=`who | grep -Eo '([0-9]{1,3}\.){3}[0-9]{1,3}'`
if ! confirm 'Confirm your IP only has access via SSH.\n Or set which one(s)' $IPS; then
IPS=$REPLY
fi

run
bash vps.sh basics lowendbox
then
bash vps.sh dotdeb mysql phpfpm domain example.com

install & reconfigure dash

install lighttpd

My sites goes online and after 5 min
vooooillaaa,i cant ssh my server and scftp

reboot,and the problem still exist

From what i remember,i use the same installation for my nginx server and it runs well
any suggestion,critism,comment are welcome

Damian

@MeMyselfandLinux said: reboot,and the problem still exist

Is sshd running?

speckl

Maybe you should use apt-get. I don't trust most other peoples scripts.

DimeCadmium

Easiest solution is likely to be:

rm /etc/xinetd.d/dropbear
update-rc.d dropbear defaults
/etc/init.d/dropbear start

Assuming I'm understanding what you did.

vedran

Login to your VPS using console in Solus.
Edit /etc/xinetd.d/dropbear and remove this line: only_from =
restart xinetd (/etc/init.d/xinetd restart)

Try to log in using ssh now

MeMyselfandLinux

@vedran said: Login to your VPS using console in Solus.

Edit /etc/xinetd.d/dropbear and remove this line: only_from =
restart xinetd (/etc/init.d/xinetd restart)

Try to log in using ssh now

Thanks a lot
problem solved

thank you everyone

TigersWay

@vedran said: Login to your VPS using console in Solus.

Edit /etc/xinetd.d/dropbear and remove this line: only_from =
restart xinetd (/etc/init.d/xinetd restart)

Nice to see someone reading the question :-)

TigersWay

@MeMyselfandLinux said: Recently i install my vps with tiger's script

https://github.com/TigersWay/VPS

removing the part

IPS=who | grep -Eo '([0-9]{1,3}\.){3}[0-9]{1,3}'

if ! confirm 'Confirm your IP only has access via SSH.\n Or set which one(s)' $IPS; then
IPS=$REPLY
fi
run

Wondering why you had to delete that part... and not simply answer "No"? Just asking to improve my set of scripts.

Glad anyway you managed to solve your problem :-)

MeMyselfandLinux

Oh hi
sorry for late replies

i really like your script,it help me to learn shell,
because ,you see ...
i am new to this penguin land

and yes,i remove that line because in here (indonesian) its hard to get static IP
at least for university student like me

so i think it is a very good idea to implement known host as optional setting
i mean like,i can pass that option through

TigersWay

@MeMyselfandLinux said: i really like your script,it help me to learn shell,

because ,you see ...
i am new to this penguin land

I was new not so long ago :-)

@MeMyselfandLinux said: so i think it is a very good idea to implement known host as optional setting

i mean like,i can pass that option through

Not so far from you, Thailand has the same kind of trouble. But you still can and should use that option: You can probably block everything but your own provider: search for "only_from" in the xinetd man page

DimeCadmium

@TigersWay said: But you still can and should use that option

Not to start a war, but (IMO) the best thing is to just turn off password auth. Chances of someone else having your key from another range is highly unlikely, unless you use the key on an infected computer, in which case they can simply tunnel it through the infected computer. AND having it open to other IP's allows you to log in if, say, you're on your laptop at someone else's house. I personally have all my servers in a VPN anyway, so they will (soon) be limited to VPN IP's, but that's not a good solution for most people, but nor is this... again IMO