Scaleway Installation problem Ubuntu 20.04 and others  [SOLVED]

sanxh
Posts: 30
Joined: Tue 12. May 2020, 11:52

Scaleway Installation problem Ubuntu 20.04 and others

Post by sanxh »

I installed KeyHelp 20.2 on Hetzner cloud and worked well, also tested on Vultr and Linode and HostHatch.com
Scaleway errors on Ubuntu 20.04:
  • Firewall not installed
  • Email Protection not installed
  • Private IP in panel instead of public IP
Please help.
Last edited by sanxh on Mon 10. Aug 2020, 22:57, edited 1 time in total.
nikko
Posts: 914
Joined: Fri 15. Apr 2016, 16:11

Re: Scaleway Installation problem Ubuntu 20.04 and others

Post by nikko »

I don't know the provider. But if you see, it's not a problem of KH, it's a problem with this provider.
Maybe a not supported virtualization, or what's ever.
The software said: Requires Win Vista®, 7®, 8® or better. And so I installed Linux.
User avatar
Alexander
Keyweb AG
Posts: 3810
Joined: Wed 20. Jan 2016, 02:23

Re: Scaleway Installation problem Ubuntu 20.04 and others

Post by Alexander »

Hello,
Firewall not installed
This is intended, since Ubuntu 20.04 comes without a preconfigured firewall, as Debian 10 does.
An appropriate firewall management will most likely be part of KeyHelp 20.3.

(It is a bug that there is a link to the firewall in the navigation of systems with Ubuntu 20.04)
Email Protection not installed
Please check the install.log and see, what causes the error (Search for "Error detected"). You can also see the skipped install steps there to later fix the error manually.
Mit freundlichen Grüßen / Best regards
Alexander Mahr

**************************************************************
Keyweb AG - Die Hosting Marke
Neuwerkstr. 45/46, 99084 Erfurt / Germany
http://www.keyweb.de - http://www.keyhelp.de
**************************************************************
sanxh
Posts: 30
Joined: Tue 12. May 2020, 11:52

Re: Scaleway Installation problem Ubuntu 20.04 and others

Post by sanxh »

exec | mkdir -p -m 0755 /etc/nftables/

files | nftables/nftables.conf => /etc/nftables.conf
files | nftables/fail2ban.conf => /etc/nftables/fail2ban.conf

exec | nft -f /etc/nftables/fail2ban.conf
/etc/nftables/fail2ban.conf:4:1-2: Error: Could not process rule: Operation not supported
table ip fail2ban {
^^
/etc/nftables/fail2ban.conf:5:11-15: Error: Could not process rule: Operation not supported
chain input {
^^^^^

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ERROR DETECTED <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
sanxh
Posts: 30
Joined: Tue 12. May 2020, 11:52

Re: Scaleway Installation problem Ubuntu 20.04 and others

Post by sanxh »

An appropriate firewall management will most likely be part of KeyHelp 20.3.
WHEN will you release this verion?
User avatar
Alexander
Keyweb AG
Posts: 3810
Joined: Wed 20. Jan 2016, 02:23

Re: Scaleway Installation problem Ubuntu 20.04 and others

Post by Alexander »

I think you need to provide the full install.log - as I can not see, whey the error is triggered. Maybe there was an error in advance.
I can perform the command "nft -f /etc/nftables/fail2ban.conf" just fine on my test Ubuntu 20 server.
WHEN will you release this verion?
There is no ETA yet - expect something during September, but that doesn't necessarily have to be the case.
Mit freundlichen Grüßen / Best regards
Alexander Mahr

**************************************************************
Keyweb AG - Die Hosting Marke
Neuwerkstr. 45/46, 99084 Erfurt / Germany
http://www.keyweb.de - http://www.keyhelp.de
**************************************************************
sanxh
Posts: 30
Joined: Tue 12. May 2020, 11:52

Re: Scaleway Installation problem Ubuntu 20.04 and others

Post by sanxh »

Also KeyHelp Scaleway Debian or Ubuntu does not show public IP only private IP.
Public IP is 51.15.99.143 but shows 10.19.134.167 :!:

:arrow:
https://intodns.com/anyfile.site
Attachments
wrong-ip-scw.png
wrong-ip-scw.png (6.36 KiB) Viewed 6784 times
User avatar
Tobi
Community Moderator
Posts: 2812
Joined: Thu 5. Jan 2017, 13:24

Re: Scaleway Installation problem Ubuntu 20.04 and others

Post by Tobi »

The ip listed in the dashboard is stored in the database.
If your ip ever changes, the database-ip will not be updated.
Gruß,
Tobi


-----------------------------
wewoco.de
Das Forum für Reseller, Digital-Agenturen, Bildschirmarbeiter und Mäuseschubser
User avatar
OlliTheDarkness
Posts: 1854
Joined: Tue 14. Aug 2018, 16:41
Location: Essen (NRW)

Re: Scaleway Installation problem Ubuntu 20.04 and others

Post by OlliTheDarkness »

Tobi wrote: Sat 15. Aug 2020, 12:09 The ip listed in the dashboard is stored in the database.
If your ip ever changes, the database-ip will not be updated.
Check beforehand in the settings whether the public IP is also selected there.

Settings >> Configuration >> System >> IP-Address

If something is true, unfortunately I have the German version :lol:
Mit freundlichen Grüßen
OlliTheDarkness

**************************************************************
Helden leben lange, Legenden sterben nie

:!: World Hack Organization :!:
**************************************************************
sanxh
Posts: 30
Joined: Tue 12. May 2020, 11:52

Re: Scaleway Installation problem Ubuntu 20.04 and others

Post by sanxh »

Screenshot_20200815-150652_Chrome.jpg
]In setting also private/internal IP, not public IP.
Scaleway Debian 10
User avatar
OlliTheDarkness
Posts: 1854
Joined: Tue 14. Aug 2018, 16:41
Location: Essen (NRW)

Re: Scaleway Installation problem Ubuntu 20.04 and others

Post by OlliTheDarkness »

sanxh wrote: Sat 15. Aug 2020, 12:34 Screenshot_20200815-150652_Chrome.jpg]In setting also private/internal IP, not public IP.
Scaleway Debian 10
Then Tobi is probably right.
This means that your public IP was not connected at the time of installation.
Since your internal IP is now in KeyHelp, you probably created the system via NAT and only then activated your public IP.
For general security, please check on the shell whether your public IP is also available on the server (ip addr).
If so, open phpMyAdmin, go to the keyhelp database, table settings and search ips (name) - dns (category). There you exchange your private IP for your public IP or enter it in addition.
Mit freundlichen Grüßen
OlliTheDarkness

**************************************************************
Helden leben lange, Legenden sterben nie

:!: World Hack Organization :!:
**************************************************************
User avatar
Alexander
Keyweb AG
Posts: 3810
Joined: Wed 20. Jan 2016, 02:23

Re: Scaleway Installation problem Ubuntu 20.04 and others

Post by Alexander »

Manually editing of the KeyHelp database settings table in regards of IP addresses should not be needed anymore. That's why there is the already mentions configuration option at:

Settings -> Configuration -> System -> IP-Address

KeyHelp checks there for all IP addresses, which currently are not in use by KeyHelp. It uses the following command:

Code: Select all

hostname -I
As long as this command will not return the desired IP addresses, they will not be recognized by KeyHelp.


Are your IPs setup within your /etc/hosts?
If not you may need to update it there to make it show up on the configuration page.
Mit freundlichen Grüßen / Best regards
Alexander Mahr

**************************************************************
Keyweb AG - Die Hosting Marke
Neuwerkstr. 45/46, 99084 Erfurt / Germany
http://www.keyweb.de - http://www.keyhelp.de
**************************************************************
sanxh
Posts: 30
Joined: Tue 12. May 2020, 11:52

Re: Scaleway Installation problem Ubuntu 20.04 and others

Post by sanxh »

Hi guys, :?:
Have you ever created a server and installed KeyHelp on Scaleway Cloud?
It is good but the problem is the internal IP instead of public IP.
Also Plesk emails not marked spam as Keyhelp does. I did everything until I got 10/10 on mail-tester.com for KeyHelp email, but unfortunately it is marked as spam in Hotmail and Yahoo Mail.

Please write your opinion here.
Thanks.

P.S.
I have tested a lot of control panels, I like only KeyHelp, Plesk and cPanel. :D :D :D
Currently running Afghan.af and Webhotpix.com
nisompic
Posts: 4
Joined: Sun 13. Sep 2020, 00:51

Re: Scaleway Installation problem Ubuntu 20.04 and others  [SOLVED]

Post by nisompic »

The internal IP shown instead of the public IP is a direct result of Scaleway's network architecture.
With their public cloud instances, public IPs are actually NATed one-to-one on the private IP of the instance.

In the case of KeyHelp, since the public IP is nowhere to be found in the OS network interfaces, KeyHelp cannot know what the public IP is (though theoretically, it could by querying this information from the outside).

You cannot replace the private IP on the instance without completely breaking networking on it.
What you can do, however, is assigning the public IP on an "alias interface" on the OS.

For example, imagine my Scaleway instance has private IP 10.65.45.25 and public IP 51.158.128.50, the initial network configuration might look like this:

Code: Select all

$ ifconfig ens2
ens2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.65.50.27  netmask 255.255.255.254  broadcast 10.65.50.27
What you would do then is assign the public IP on an alias interface, like so:

Code: Select all

$ ifconfig ens2:0 inet 51.158.128.50 netmask 255.255.255.255
Which would give you:

Code: Select all

$ ifconfig ens2:0
ens2:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 51.158.128.50  netmask 255.255.255.255  broadcast 51.158.127.45
If you need persistence, you can create a new .cfg file in /etc/network/interfaces.d, for example /etc/network/interfaces.d/60-keyhelp.cfg, with the following contents:

Code: Select all

auto ens2:0
iface ens2:0 inet static
    address 51.158.128.50/32
Save the file, and reboot the instance.

KeyHelp will now offer both the private and the public IP in the configuration interface. You can simply uncheck the private IP and keep the public IP.

Cheers!

EDIT: I also found out why the firewall installation was not working properly on Scaleway's Ubuntu 20.04:

Code: Select all

root@testkh:~# grep CONFIG_NFT_ /boot/config-5.4.0-1018-kvm
root@testkh:~# find /lib/modules -name "*nf_tables*"
root@testkh:~# modprobe nf_tables
modprobe: FATAL: Module nf_tables not found in directory /lib/modules/5.4.0-1018-kvm
The nf_tables module isn't built with their kernel which is why the installer cannot apply rules.
Might be worth requesting this to their team.

You could also rebuild the kernel after configuring the correct options to build the nf_tables module.
Last edited by nisompic on Sun 13. Sep 2020, 01:47, edited 2 times in total.
sanxh
Posts: 30
Joined: Tue 12. May 2020, 11:52

Re: Scaleway Installation problem Ubuntu 20.04 and others

Post by sanxh »

nisompic wrote: Sun 13. Sep 2020, 01:09 The internal IP shown instead of the public IP is a direct result of Scaleway's network architecture.
With their public cloud instances, public IPs are actually NATed one-to-one on the private IP of the instance.

In the case of KeyHelp, since the public IP is nowhere to be found in the OS network interfaces, KeyHelp cannot know what the public IP is (though theoretically, it could by querying this information from the outside).

You cannot replace the private IP on the instance without completely breaking networking on it.
What you can do, however, is assigning the public IP on an "alias interface" on the OS.

For example, imagine my Scaleway instance has private IP 10.65.45.25 and public IP 51.158.128.50, the initial network configuration might look like this:

Code: Select all

$ ifconfig ens2
ens2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.65.50.27  netmask 255.255.255.254  broadcast 10.65.50.27
What you would do then is assign the public IP on an alias interface, like so:

Code: Select all

$ ifconfig ens2:0 inet 51.158.128.50 netmask 255.255.255.255
Which would give you:

Code: Select all

$ ifconfig ens2:0
ens2:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 51.158.128.50  netmask 255.255.255.255  broadcast 51.158.127.45
If you need persistence, you can create a new .cfg file in /etc/network/interfaces.d, for example /etc/network/interfaces.d/60-keyhelp.cfg, with the following contents:

Code: Select all

auto ens2:0
iface ens2:0 inet static
    address 51.158.128.50/32
Save the file, and reboot the instance.

KeyHelp will now offer both the private and the public IP in the configuration interface. You can simply uncheck the private IP and keep the public IP.

Cheers!

EDIT: I also found out why the firewall installation was not working properly on Scaleway's Ubuntu 20.04:

Code: Select all

root@testkh:~# grep CONFIG_NFT_ /boot/config-5.4.0-1018-kvm
root@testkh:~# find /lib/modules -name "*nf_tables*"
root@testkh:~# modprobe nf_tables
modprobe: FATAL: Module nf_tables not found in directory /lib/modules/5.4.0-1018-kvm
The nf_tables module isn't built with their kernel which is why the installer cannot apply rules.
Might be worth requesting this to their team.

You could also rebuild the kernel after configuring the correct options to build the nf_tables module.
This helped me so much, thanks
Locked