I tested the .ova template using a live domain and public ip on VMWare Fusion. The installation when smoothly, however I did get a few issues with the options I selected:
Installation of office reported ok in the installation, but when log into nextcloud browser after saving the require office extensions and trying to open a .odt document, I get a message " Onlyoffice cannot be reached. Please contact admin". I went to apps and notice that “Community Document Server” was not installed even though during the office installation it gave the impression it was installing, however when I try to download/enable from browser I get the following message "cURL error23: Failed writing body (9956!= 16360) (see http://curl.haxx.se/liburl/c/libcurl-errors.html)
The installation of talk failed, it detected that port 5749 was close, and I know is open.
Samba shares failed during initial installation, did not detect the share directory i put.
Installation is much smoother than your previous Nextcloud_VM_www.hanssonit.se.ova, many tks for the great work! My server is up and running, but I cannot get self-signed certificates to work, so it is inaccessible to the Internet.
I am fairly new to NC and did not succeed with tls, probably because my free domain is through no-ip. The installation message suggests "Please try to run it again some other time […/activate-lts.sh]. But when I do so I get 6 errors like /var/scripts/activate-tls.sh: line 13/16/38/40/7/54/59: debug_mode: command not found, similar root_check, msg_box, ask_yes_or_no
When I installed NC via snap I was able to generate self-signed certificates with sudo nextcloud.enable-https self-signed
Strange, because everything checks out when I try it.
Onlyoffice is a pretty huge file and the app server might be slow to download from, so the “bug” isn’t specific to the 20.04 VM, it’s just a Nextcloud thing in general. There have been reports about that before in the server repo afaik.
I would say that’s impossible. The open port check happens externally, so if the port check says it’s closed, it’s closed. To be more specific, we check against https://www.yougetsignal.com/tools/open-ports/ - does it say closed there as well?
You don’t need to generate a self signed certificate, it’s already configured and setup. We use the default ones in Ubuntu, and the Apache configs are already set up to use them if you don’t choose to generate a valid TLS certificate (which I highly recommend)
@eced77 have you tried using the ipaddress of your smb-server like proposed: //ip-address/share and can you ping the smb-server from your nextcloud-server?
Also, have you enabled smb3 for your smb-server?
On what OS is your smb-server running?
And can you mount the share from the smb-server successfully on another device?