NS8: Configure NGINX fails

The error is still reproducible ?

Yes, it is.

EDIT:

The error also occurs when using Rocky 9.1 without upgrading to 9.2.
After installing the webserver, configuration works but after reboot it doesn’t work anymore.

1 Like

could you try with a minimal installation iso of rocky linux then initiate the cluster ?

web server 1.0.3 install log on VM 4 cores and 8GB RAM rocky-linux minimal install

configure webserver

I cannot reproduce your issue

Question :smiley:
why do you have made your prebuilt image why do you not use the official prebuilt image ?

I just converted the official qcow2 image to vmdk to be able to use it with vmware, see NS8: All VMWare images unusable - #10 by mrmarkuz
I didn’t build an image.

I’m going to test Rocky from ISO later today…

2 Likes

the boot stucks on probing EDD(edd=off to disable)

If you’re using ESXi/Workstation you need to set the hard disk on an IDE controller,

EDIT:

Related issue:

What exactly did you try?

2 Likes

yes I set SATA on proxmox, also I changed the cpu default type KVM64, for now I test the qcow

If using RHEL distro like Rocky on Proxmox you need to change CPU to something else, see Installation — NS8 documentation

When using RHEL-based images on Proxmox, change the default CPU model to anything other than kvm64

I use SandyBridge or G5_Opteron, depending on CPU. Host should work too.

1 Like

honestly I am not a big fan of prebuilt image :confused:

what is the default partition size ?

1 Like

The default size is 10GB. I kept it even if 20GB is the minimum requirement.
After resizing the disk you need to start the VM twice, the first time it doesn’t boot.

2 Likes

well still not fan of it :smiley:
However with the qcow image web server is up and configured smoothly

1 Like

4 core and 8 GB of ram, however few used :smiley: 1.2G

1 Like

Can still re-create the “Connection reset by peer” error starting from the Rocky ISO:

  • Install Rocky 9.1 minimal from ISO
  • Reboot
  • Install NS8 via curl, which also upgrades Rocky to 9.2, so
  • Reboot
  • Create cluster leader via command
  • Logon to UI
  • Install NGINX
  • Configure NGINX
  • Hit “Save” on SFTPGO configuration
  • Something went wrong

Cheers.

1 Like

What error ?

What ressources for the VM ?

What ressources for the hypervisor ?

I am guessing if you have ssd or hardrive on the hypervisor

The same Connection refused as above.

2 core, 4GB

8 core, 16GB

Not sure it would work without one. :grinning: Mine is a harddrive.

Cheers.

with SSD ?

No, all spinning disks.

Cheers.