Seup and Document server #480

Closed
opened 2026-04-21 12:48:42 +00:00 by c24elipe · 10 comments
Collaborator

This is mainly meant to be a quick summary and description of the hosting server configuration as it is being set up.
For password or other details, please contact @c24elipe

This is mainly meant to be a quick summary and description of the hosting server configuration as it is being set up. For password or other details, please contact @c24elipe
c24elipe changed title from Document server setup! to Seup and Document server 2026-04-21 12:49:06 +00:00
Author
Collaborator

I have updated the SSH port to instead be on port 2222 (This port was chosen because it is an alternative port for SSH)

Why?
I did this to be able to block the 22 (SSH default port) since this port is often attacked by bots and similar threats that look for insecure SSH setups. This is not much safer against a human (who can scan for open ports), but slightly safer against automatic attacks that look for attack vectors.

To change this back, look at "/etc/ssh/sshd_config"
OBS, make sure the new port isn't blocked by the UFW firewall!

I have updated the SSH port to instead be on port **2222** (This port was chosen because it is an alternative port for SSH) Why? I did this to be able to block the 22 (SSH default port) since this port is often attacked by bots and similar threats that look for insecure SSH setups. This is not much safer against a human (who can scan for open ports), but slightly safer against automatic attacks that look for attack vectors. To change this back, look at "/etc/ssh/sshd_config" **OBS**, make sure the new port isn't blocked by the UFW firewall!
Author
Collaborator

I then followed the docker install documenation found at https://docs.docker.com/engine/install/ubuntu/

Docker compose is then inlcuded.

I then followed the docker install documenation found at https://docs.docker.com/engine/install/ubuntu/ Docker compose is then inlcuded.
Author
Collaborator

Then node was installed using the offical website:
http://nodejs.org/en/download

Then node was installed using the offical website: http://nodejs.org/en/download
Author
Collaborator
To install the dotnet dependencies, I used the official Microsoft guide: https://learn.microsoft.com/en-us/dotnet/core/install/linux-ubuntu-install?tabs=dotnet10&pivots=os-linux-ubuntu-2204
Author
Collaborator

Copied over public key using ssh-copy-id,
and set the following for exsta security.

PermitRootLogin no
StrictModes yes
PasswordAuthentication no
PermitEmptyPasswords no
X11Forwarding no

Now the private key is needed to log in

Copied over public key using ssh-copy-id, and set the following for exsta security. PermitRootLogin no StrictModes yes PasswordAuthentication no PermitEmptyPasswords no X11Forwarding no Now the private key is needed to log in
Author
Collaborator

I then enable UFW (the firewall) with a single rule: ufw allow 2222.

Also ran:
ufw default deny incoming
ufw default allow outgoing

image

The plan is to poke holes for the frontend later

I then enable UFW (the firewall) with a single rule: ufw allow 2222. Also ran: ufw default deny incoming ufw default allow outgoing ![image](/attachments/79a431c4-dc4f-4a8c-a776-18f97a3400cb) The plan is to poke holes for the frontend later
Author
Collaborator

I have not set a root password.

For it, ask me, or Henrik (I will tell him later during our meeting)

I have not set a root password. For it, ask me, or Henrik (I will tell him later during our meeting)
Collaborator

This implementation looks solid. The use of SSH key authentication, disabling password login, and configuring the firewall with a default deny policy are all good security practices. Also using official documentation is reliable and correct.

The updated SSH port to 2222 instead of 22 is a security through obscurity approach. This can help against automated bot attacks but can not be a strong protection on its own. It does not help as much against targeted attacks. it is used good In this implementation as it is used with a stronger security messearue such as ssh keys.

Overall this is a good initial setup. This would be stronger with the addition regular system updates as it is important for the system to patch security vulnerabilities.

This implementation looks solid. The use of SSH key authentication, disabling password login, and configuring the firewall with a default deny policy are all good security practices. Also using official documentation is reliable and correct. The updated SSH port to 2222 instead of 22 is a security through obscurity approach. This can help against automated bot attacks but can not be a strong protection on its own. It does not help as much against targeted attacks. it is used good In this implementation as it is used with a stronger security messearue such as ssh keys. Overall this is a good initial setup. This would be stronger with the addition regular system updates as it is important for the system to patch security vulnerabilities.
Collaborator

@a24danwe this issue can be close?

@a24danwe this issue can be close?
Collaborator

Yes!

Yes!
Sign in to join this conversation.
No milestone
No project
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K#480
No description provided.