Using Collabora with MAIB NextCloud?

Unsupported Modifications
16

Both servers on DO (Digital Ocean).

MiaB:
box:~# lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty

Collabora:
office:~# lsb_release -a
Distributor ID: Ubuntu
Description: Ubuntu 16.04.4 LTS
Release: 16.04
Codename: xenial

Yeah, the problem in terms of my email address not appearing valid, was thus:

  1. Loaded older snapshot of MiaB on DO (the one I took after enabling admin rights, but before installing collabora).
  2. Got DNS errors trying to install letscrypt (similar to above error message - instead of email issue, it was DNS and MX records issues).
  3. Made DNS changes in both DO and my registrar (Zuver).
  4. Temporarily resolved DNS issues (based on the system checks at box.hostname.com/admin) only to have somehow cause MX DNS record issues.
  5. Re-ran ‘sudo mailinabox’ and thought I got DNS back up. I guess I was wrong.

DNS Settings for both Zuver and DO, as we speak:

Zuver:

DO: Domains and DNS Records

box.hostname.com:

NS ns2.box.hostname.com points to MiaB IP on DO
NS ns1.box.hostname.com points to MiaB IP on DO
A box.hostname.com points to MiaB IP on DO
A www.box.hostname.com points to MiaB IP on DO

office.hostname.com:

NS office.hostname.com points to ns2.box.hostname.com
NS office.hostname.com points to ns1.box.hostname.com
A wwww.office.hostname.com points to Collabora IP on DO
A office.hostname.com points to Collabora IP on DO

I think that’s as much info as you’ve asked. If you need more, please let me know. I am techy but not so great with DNS - especially after hours of bashing my head against a brickwall.

I still can’t get SSL setup - I’ve tried letsencrypt and also certbot (I think they’re both the same project at the core - but I could be wrong). Either way, I am getting similar errors from both.

e.g.

office:~# sudo certbot --nginx -d office.hostname.com Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator nginx, Installer nginx Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org Obtaining a new certificate Performing the following challenges: http-01 challenge for office.hostname.com Using default address 80 for authentication. nginx: [warn] conflicting server name "office.hostname.com" on 0.0.0.0:443, ignored Waiting for verification... Cleaning up challenges nginx: [warn] conflicting server name "office.hostname.com" on 0.0.0.0:443, ignored Failed authorization procedure. office.hostname.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for office.hostname.com

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: office.hostname.com
    Type: connection
    Detail: DNS problem: NXDOMAIN looking up A for office.hostname.com

    To fix these errors, please make sure that your domain name was
    entered correctly and the DNS A/AAAA record(s) for that domain
    contain(s) the right IP address. Additionally, please check that
    your computer has a publicly routable IP address and that no
    firewalls are preventing the server from communicating with the
    client. If you’re using the webroot plugin, you should also verify
    that you are serving files from the webroot path you provided.

I reckon it has something to do with configuring name servers on Zuver, I don’t know how else to set things up there - it seems really confusing, but I’m also no expert.

root@office:~# host ns1.hostname.com
Host ns1.box.hostname.com not found: 2(SERVFAIL)
root@office:~# host ns2.hostname.com
Host ns2.box.hostname.com not found: 2(SERVFAIL)

Would appreciate any assistance you could provide.

Thank you!!! :slight_smile: