Selfhosted

60210 readers

875 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

What do I do -- Incorrect? (sh.itjust.works)

submitted 1 year ago by CraigCabbage@sh.itjust.works to c/selfhosted@lemmy.world

11 comments fedilink hide all child comments

I tried installing YunoHost once, now I'm installing again. I installed it on a Virtual Machine. After installing, it asked for a user and password. I typed in what was provided "root" and "yunohost", and it didn't work, it said incorrect.

you are viewing a single comment's thread
view the rest of the comments

[–] irmadlad@lemmy.world 1 points 11 months ago

The same thing can happen even when you are first doing the setup process.

I might get a bit too stressed about standing up a server than I should, but this notion has always been in the back of my mind, prompting me to hurry the fuck up and secure everything before some bot detected I was remiss we in having this or that in place in the initial setup. So, it's like a sprint trying to get all security in place.

I don't share my servers with others like a lot you guys do, so it's a little simpler. Implementing host.allow and host.deny (ALL:ALL) does the trick. Over the course of 24 hours, I think, conservatively hundreds of bots visit.