NC 30.0.1: "Could not check for otf loading support."

ℹ️ Support
,
1

I upgraded vom NC 28 to 30.0.1 and see this warning in the admin panel:

Could not check for otf loading support. Please check manually if your webserver serves .otf files. To allow this check to run you have to make sure that your Web server can connect to itself. Therefore it must be able to resolve and connect to at least one of its trusted_domains or the overwrite.cli.url. This failure may be the result of a server-side DNS mismatch or outbound firewall rule. For more details see the documentation :arrow_upper_right:.

My webserver allows serving .otf files. Also, the stated possible causes for this warning why the automatic test may fail do not apply:

  • My web server can connect to itself (both via loop back, i.e. 127.0.0.1 and ::1 as well as its public IP addresses).
  • There is a forward (A and AAAA) and reverse (PTR) DNS entry which points to the public IP addresses
  • The DNS entry matches the trusted domain
  • There is no firewall at all

What triggers this warning? How do I get rid of the warning?

1 Like
2

I had the same exact error as you described. This is how I fixed it:
Go to your /etc/apache2/sites-available Nextcloud.conf file and change the following:

<Directory /var/www/nextcloud>
        Options Indexes FollowSymLinks
        AllowOverride **None**
        .....
    </Directory>

to:

<Directory /var/www/nextcloud>
        Options Indexes FollowSymLinks
        AllowOverride **All**
        .....
    </Directory>
3

The fix was much easier. The value for the settings trusted_domains in config.php was wrong. It listed all domain names for my server, incl. DNS CNAME entries, but not all of them actually served my NC instance due to virtual name hosting.

That is a bad advice security wise. This basically means that all options can be overriden by local configurations even risky options.

4

Apologies but I would have to disagree based on Apache2.4 recommendations (https://httpd.apache.org/docs/current/upgrading.html). Besides, in my case Nextcloud is not front facing and behind a firewall. Glad you were able to fix yours another way.

5

Yes, and that’s done specifically through .htaccess files, but only for that virtual host under that specific directory, and you usually want that because it saves you a lot of configuration work.

If you don’t trust the .htaccess files provided by the application, you can of course set AllowOverride to None and then manually configure everything that is in the .htaccess file, but then I wonder why you would use an application you don’t trust in the first place :wink: