As the titles says, it would be nice if Post4VPS could create fancy back-link tags for its own website and its sponsors that we could embed on our services hosted inside the sponsored VPS.
Why?
Well, right now the back-links are likely done with a simple html link element, but to get better visibility it could be a fancy banner or something like that. I mean, if we get this website to get more views we will get a bigger community and it will be more fun
I am not a graphical designer nor I have any good artistic skill, so I am unfortunately unable to provide any sample. 

So, if you got good designer skills, show us what you can do!

Just a little note: to be able to use the banner on a better way it is recommended, but not mandatory, to create vectorial images instead of raster ones.

Hello beautiful people i'm back.
for those who doesn't know me, my name is Mohamed i'm from Tunisia, i'm a future computer science student. i joined this forum around 8 months later i quit for my studies now i back because i got time to spent here.
i missed this forum guys , long time no see if there is anything changed in this forum please let me know and thanks a lot.

Just a suggestion also about review section, might be add a tag for each sponsor also works? This will give an advantage for sponsor too. So if users want to see a review for X sponsor, they can go for it. I also see some VPS holders review without sponsor name in their title, might not too important, but if using tag for each sponsor, we can know which VPS belong to which sponsor. Just my opinion :p.

Is there any scope for adding an Index thread for VPS Review section?
The purposes of this suggestion is as follows:
 -> To help users to select the vps by reading reviews from  other users.
 -> To keep updated  with VPS Plans(Current issue  is some VPS which the sponsorship has already ended, is replaced by some other providers and the reviews are still about the old VPS Plan, for example VPS 3 Review).
-> To keep  the section ordered.
-> To appreciate the reviewers.
Please comment your views.
Thank you.

cold autumn winds, outside,
knocking, on and on, days and night !

in the deep dark lap of the sky,
countless stars, frozen drops of light !!

A lover, roams and roams, alone, down below on Earth..

Endless, unforgiving, old and cold, the path..

Everyone has warned him again and again,

That all this, futile, nothing to lose or gain,

That no matter how much you search and search,

will end up at last, exactly where you start.

But he is happy, for there will always be lands to explore,

That all roads lead to the infinite magical shore..



.....
I'm posting it here, cause this is partly an expression of how i view life.

It started as an attempt to translate a Bengali poem i love so much.

I will give anyone an upvote if you can guess the writer or the poem that I wanted to translate, from those two lines at the start.

please forgive errors. correct anything you deem should be corrected.

thanks for reading.

As the title suggests, is there a limit in time on which 2 consecutive posts won't be merged together as one?..

I'm under the impression that the forum doesn't have one. And I suspect that's on purpose to avoid users abusing their post counts. Well, that can perhaps make sense for those with a VPS and are struggling to meet their quota BUT not that much for the others.

I've repeatedly went through the unpleasant experience when doing a second (intentionally independent) post, even after 24 hours or so, to find out that it's merged with the preceding one.

Can you please fix this?

Hello,

I'm running into errors with my VPS 9 while trying to RDP. I installed XRDP and TigerVNC and proceeded with the installation of XFCE desktop environment. However, here's the strange thing that's happening. I am able to get the XRDP login screen and after a successful login, I am just getting a black screen and the session disconnects.

I googled a few articles on the web and a few bug fixes ask us to comment out the line `channel_code=1` in `/etc/xrdp/xrdp.ini` however, to my dismay there's no such line in the config file.

As a side note, the last time GNOME did work as a desktop environment on my VPS. This time I installed XFCE as it is lighter than GNOME, which was hogging resources on my VPS the last time. After the latest OS installation, I'm facing this problem, dunno if it's related to XFCE particularly. BTW SELinux is disabled on my VPS.

Hope y'all are able to help me.

Regards,

• 4x VPS 1
  
• 2x VPS 3
  
• 1x VPS 8
  
• 1x VPS 9 (Location: Phoenix) (Note: Detailed justification needed for using large specs)
  
• 2x VPS 10
  
• 1x VPS 11
  
• 1x VPS 12
  

We're aiming at a date of around 5th of April for announcing the winners.  VPSs will be allocated soon after.

For comparing the VPS Specifications, Users can check https://post4vps.com/compare/#1,3,8,9,10,11,12

PLEASE READ AND UNDERSTAND THE TERMS AND CONDITIONS OF THE SPONSOR BEFORE YOU APPLY - REFER BELOW:

• Users must read and agree to all terms of the SPONSOR (of the VPS which they want) when they apply.  These can be found on our Plans Page.  
  
• When you apply, please let us know your preferred OS and the Domain you will be using with the VPS.
  

Please Read before Applying

1. Read Our Forum Rules before applying.
   
2. You should have met our minimum requirements to get VPS.
   
3. Read Application Format before applying. (If the application format is wrong then your Request will be rejected)
   
4. You must post your VPS application in VPS Request Forum.
   
5. Read TOS of VPS providers before applying.
   

This is Part 2 of my documentation of my experience with EUServ free VPSs, but this time from the stand point of running Fedora 30 (for the perspective of them/VPSs being IPv6-only, see Part 1: Running an IPv6-only VPS Gotchas! )

The use of EUServ's VPSs allowed me to experience not only the challenges of running an IPv6-only VPS but also to have a first-hand account of running Fedora 30 inside an LXD/LXC container.

1- A Bit of Context
First I should mention that LXC is a well-established, low-level Linux container runtime, dating back to 2008; thus well before anyone even heard about the currently widely used Docker alternative (which saw light in 2013.) The problem with LXC containers was/is(/will always be) its sheer complexity because of it being that low-level. Enter LXD (in 2015), which is Canonical's effort to make LXC container accessible by building an API around it in Go language; in this sense, LXD is a container orchestration engine with LXC under-the-hood.

LXD containers can only run Linux operating systems, and being containers suggest that its VMs share all the devices with the host operating system. I explicitly state this because, sysadmins should always remember this when on such VPSs.

With this out of the way now is the time to do all the routines of taking control of a brand new VPS running Fedora 30(+) or CentOS (7, 8 +).

2- Running a Properly Managed VPS
In this section, I'll go through all the steps essential to properly administer any RedHat-based system with few tips that are specific to EUServ Fedora 30 template used in their automation process.

2.1- Secure Your VPS
It's always a good practice to check first on the VPS's datetime and see if it's accurate. In our case here -ie LXD Container- time settings is the Host's prerogative, so we'll just check and may be change the timezone if feel like it.

To modify the timezone:

You can also change the hostname, but I won't do it here:

2.1.1- Disable Root Login
The absolute first thing to do is to remove the root login via SSH, but to be able to do that, we first need to create a user with sudo power (ie, a sudoer.) For clarity, I'll use the standard 3 steps in Fedora.

Now, you can test that your 'sudoer' is functioning, by just login out and relogin as your newly created 'super-user', then try to switch as root:

If you become 'root' after running the command above, then you're all set and you can now go ahead and disable the root login via SSH, by modifying the adhoc line in the '/etc/ssh/sshd_config'
From:

To:
Then:

2.1.2- Activate the Firewall
I've noticed that Firewalld is down by default:

Here, I have to pause a second to say that till now I'm still not sure if that thrown error is expected from an LXD container OR is it a bug!.. Is it a permission issue or a misconfiguration ?.. I can't say, didn't dig deep enough!

Ok! Now, eventhough the firewall is running we have to activate it by assigning the VPS public interface to (in this use case) the public zone:

Before, there is no interface in the public zone:

To know more about your VPS net. interfaces:

Time to add the eth0 to the public zone and reload the Firewalld config

Testing the public zone again after this activation:

Now, the only available service through eth0 is the one listed above, anything else blocked!

2.1.3- Removing Password Login and Setting Up Public Key Authentication
I'll come back to this in the last section

This is the minimum required steps to take to secure your VPS. You may add other things, like running the fail2ban package or changing SSH service port, but for me those aren't really important if you do implement the above 3 mechanisms.


2.2- Update your System
Before updating this system, I'd like to make few observations:
> When you check the failed services of your VPS at its startup, you'll see this:
This is normal for an LXD container (you may add 'sys-kernel-config.mount' service to that list too). What's not normal and an indication of an unstable system is when other things fail and don't won't to restart. I'm thinking for example of one instance where I had the 'sssd.service' (ie, System Security Services Daemon) refusing to start! and it was hell to work on that system

> Being an LXD container, you don't need,,when updating your system, anything related to the kernel, filesystem etc; thus we'll exclude them from the update process, like this:

If you skip this step, expect a lot of pointless warnings during the update process.

Also, you'll notice that I've also excluded the 'sudo' package, this is because the latest version in Fedora 30 is buggy!

With all this preparation we are now ready to update our system:

That's all there is to it!

Notice specific to EUServ's Fedora 30 template:
Even though the template used is the English version, it has the 'glibc-langpack-de' package instead of the 'glibc-langpack-en', thus a warning is issued every time you interact with the shell. So, you're advised to install the English version then remove the German one to fix that issue.

My last section in this OP will be about enabling Public-key Authentication, it's the most important thing to do security-wise and thus deserve to be treated separately.

2.3- Enabling/Using Public-key Authentication
If you're logged in your VPS, logout now, and from your Linux machine (I'm not covering Windows case/Putty), check your system's entropy:
You really must have something decent here +1024, we're about to generate an ECDSA key pair for version 2 of the SSH protocol:

Tha's it!.. Now, what we need to do is send the public key of this key-pair to our VPS, which is done like so (with [email protected] being your sudoer and your VPS IP):

Now, double check that you can indeed login with that key, by login with :

If you succeed in loging in, then now is the time to disable any password authentication in the SSHD config file and restrict the in/out to the sudoer group and users (extra-security lines in the /etc/ssh/sshd_config files):
Reload the sshd daemon.

From now on your system is ALL YOURS!...

NB: Follow up to this OP will land in this thread when it's deemed important.

---

UPDATED:
A last tip I forgot to mention, given that we've already set our public-key authentication, is how to make the PPK file out of our pair-key for use with Filezilla to have an sFTP access to your VPS (or for use with Putty for those on Windows who need to use it.)

Well it's as simple as issuing this command:

I did a bit of googling about the followinf issue, mentionned above:

(03-31-2020, 01:20 PM)fChk Wrote: (...)
Mar 31 13:21:23 srvXYZ firewalld[8609]: ERROR: Failed to read file "/proc/sys/net/netfilter/nf_conntrack_helper>
Mar 31 13:21:23 srvXYZ firewalld[8609]: WARNING: Failed to get and parse nf_conntrack_helper setting

Here, I have to pause a second to say that till now I'm still not sure if that thrown error is expected from an LXD container OR is it a bug!.. Is it a permission issue or a misconfiguration ?.. I can't say, didn't dig deep enough!

The issue seems to be well known for systems with kernel 4.7 and up where "the automatic helper assignment in kernel has been turned off by default". Check 'Automatic Helper Assignment' for more on that.

Also check this discussion:
> https://github.com/lxc/lxd/issues/4006