If not, then Duplicati likely isn’t even running correctly and that needs to be addressed first.
If it is working, then something is likely going wrong with the --webservice-interface parameter or firewall settings.
Also, when you “browse to the ip of the machine” are you doing that from the same machine on which Duplicati is running or from a different machine (meaning there could be multiple firewalls involved)?
I think background output from either stdout or stderr flows to the tty, but if you have “stty tostop” it stops you. Shell job control commands vary (as do redirect ways), but “jobs” might show if the job had stopped, and “fg” might have returned it to the foreground, as if the ampersand was not used (a test we’re still waiting to hear).
Assuming things got started (including assuming the “/opt/uplicati” typo in the original wasn’t actually the run) then “netstat -a” to look for a LISTEN on port 8200 on the “*” interface would be good, then poking with telnet might come next, e.g. “telnet 127.0.0.1 8200” from FreeBSD, then try the external IP, then try from elsewhere. Even Windows comes with telnet, and I think the usual escape from any of them is Control-] followed by “quit”.
@warllo I’m glad you got your system working. Its history isn’t clear, but here are some ideas for the future.
FreeBSD 11.1 added fdatasync. Your sqlite was too new for your old version. Is your package repo set well?
I’m not a FreeBSD versioning and upgrades expert, but I’ll point to some advice to avoid issues in the future: