Server says 404 not Found for ddness.de/nextcloud/statusphp

Support intro

Everything was working fine until my provider sacked my public IPv4 needed for the DynDDS. I got it back, I had to setup a new pw for the ddnss and nearly everything is backed to normal.
I can connect via browser, the clients of my co-workers connect normally- only my own clients refuse to work because of this status.php

Any help greatly appreciated. thank you

Or for longer, use three backticks above and below the code snippet:


Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can :heart:

Nextcloud version (eg, 29.0.5): 3.13.2
Operating system and version (eg, Ubuntu 24.04): Win10
Apache or nginx version (eg, Apache 2.4.25): replace me
PHP version (eg, 8.3): replace me

The issue you are facing:

Client can’t connect: Server says 404 not Found for ddness.de/nextcloud/statusphp

Is this the first time you’ve seen this error? (Y/N): Y

Steps to replicate it:

The output of your Nextcloud log in Admin > Logging:

PASTE HERE

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

PASTE HERE

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Output errors in nextcloud.log in /var/www/ or as admin user in top right menu, filtering for errors. Use a pastebin service if necessary.

PASTE HERE

I can not see the same now but your error message states your router is unable to resolve the DNS address

now when I check

this website is hosted using self-signed certificate which is by default not trusted by clients…

mirgolem.ddnss.de uses an invalid security certificate. 
The certificate is not trusted because it is self-signed. 
Error code: [MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT](about:certerror?e=nssBadCert&u=https%3A//mirgolem.ddnss.de/nextcloud/status.php&c=UTF-8&d=%20#certificateErrorDebugInformation)

Depending on what your goal is you could add the cert to the Windows Trusted CA certificate store which likely will resolve the problem. But you will have to repeat this procedute on every device which is the reason why you should use public certificates accepted everywhere e.g. letsencrypt.org

Thank you for your answer. I will consider getting proper certificates in the future.
Atm I have to focus to get the NC client back to full functionality to continue our work.

What I am really curious about: why does the client work for my co-workers? In the end my clients aren’t any different from theirs.

look here:

https://github.com/nextcloud/desktop/issues/4

Do you want access from LAN and from internet? Please use a Lets Encrypt certificate. Maybe problems with the clients are only consequential error. Especially if you allow access from the Internet anyway, setting up Lets Encrypt is very easy. Here an instruction for Debian an here for Ubuntu.

Also, I don’t think you can really seriously run Nextcloud on “Win10”. Describe what your goal is.

??? Can you explain it?

Reconfiguring the DynDns I added both ip4 and ipv6 adresses in the update-url. My clients tried to resolve it with the ipv6 instead of the ipv4.
This was the reason why the clients of the coworkers worked manually- they connect from outside.
Removing the ipv6 was getting everything back to normal.