Nextcloud with Letsencrypt using OMV and docker-compose - Q&A

  • After correcting these right issues i could proceed and finish DB creation by Nextcloud. The user and DB was created on the MariaDB instance by the nextcloud installer-

    Nevertheless my nextcloud site now shows this:


    Code
    Internal Server Error
    
    The server encountered an internal error and was unable to complete your request.
    Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
    More details can be found in the server log.


    I could not find any related log entry....

    Any ideas?

  • How can I reattach nextcloud to mariadb since I am getting SQLite is currently being used as the backend database. For larger installations we recommend that you switch to a different database backend. This is particularly recommended when using the desktop client for file synchronisation. To migrate to another database use the command line tool: 'occ db:convert-type', or see the documentation ↗. ?

  • Is there a little guide how to setup fail2ban for this setting running nextcloud, letsencrypt and mariadb in containers? Can I use the OMV-Extras plugin directly or do I need to configure the fail2ban instance within the letsencrypt container?

    How does the latest filter have to look like? Which log-level in nextcloud is required?

    Chaos is found in greatest abundance wherever order is being sought.
    It always defeats order, because it is better organized.
    Terry Pratchett

    • Offizieller Beitrag

    It is already included:


    Zitat


    It is essentially an nginx webserver with php7, fail2ban (intrusion prevention) and letsencrypt authentication built-in.

    from: https://blog.linuxserver.io/20…crypt-nginx-starter-guide

  • Hi, I did everything as written in the macom guide, but when I want to go on nextcloud.asprodent.com.ua I get error 404

    When I go to http://nextcloud.asprodent.com.ua:81/ I get welcome screen OMV 5

    How I can fix it? How I can go welcome screen Nextcloud?

  • Hi, I did everything as written in the macom guide, but when I want to go on nextcloud.asprodent.com.ua I get error 404

    When I go to http://nextcloud.asprodent.com.ua:81/ I get welcome screen OMV 5

    How I can fix it? How I can go welcome screen Nextcloud?

    Well it is working in a way since http://nextcloud.asprodent.com.ua:81/ land on your OMV login page! LOL

  • nextcloud.subdomain.conf

  • here the way it should be 2048 is ok if you are not using arm processor otherwise 1024

  • And my php I use port 444 I do not use doker compose it might be different for you but dot forget I think you need to be able to login in your nextcloud locally before doing anything else

    • Offizieller Beitrag

    When I go to http://nextcloud.asprodent.com.ua:81/ I get welcome screen OMV 5

    It seems the port forwarding in your router is wrong.

    The outside (WAN) port 80 should be forwarded to the inside (LAN) port 81.

    Then in the letsencrypt container LAN port 81 is forwarded to the docker port 80.

    No need to change the port of OMV as on the LAN where OMV is connected the port 80 is not used.

  • I ran through this 2 times from scratch now and cannot get it to work. I am using 100% the exact same configuration as provided in the guide.

    The only difference is that i am not using docker-compose but portainer. Should not be any different i guess.

    I assumed that all containers are connected to the same bridge (for me standard bridge network) as this is not mentioned in the guide.


    The yml sample of the guide posts ports as for example:


    Code
        ports:
          - 444:443
          - 81:80


    By reading the docker-compose manual this transaltes to horst_port:container_port for portainer.

    Is that correct? Might this be wrong in the guide?

    It is beginning to be frustrating here :/


    When trying to access https://my.url/nextcloud i get a blank/white page. Looking at the html source of it, i see that it is some OMV 404 error behind.

    • Offizieller Beitrag

    ports:
    - 444:443

    This maps the port 444 in your LAN to the port 443 in the container.

    Right side of the ":" is inside the container. For ports and volumes.

    Maybe posting a screen shot of your portainer settings would help.

    Is there a reason you don't use docker-compose? For me it is much easier. Less clicks and everything on one page.

  • monsen

    docker-compose automatically creates a user-defined bridge network for all containers in the same yml file. You probably have to do this by hand or integrate it into your portioner stack. They won't find each other if they are only connected to the general bridge network.


    @dvorstov what is the output of the letsencrypt container logs?

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!