No connection with browser

Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

example

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

longer
example
here

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, 20.0.5): 21.0.0.18
Operating system and version (eg, Ubuntu 20.04): Raspberry Pi OS Buster 64bit
Apache or nginx version (eg, Apache 2.4.25): Apache/2.4.38 (Debian)
PHP version (eg, 7.4): 7.4.16

The issue you are facing:
After having been off some hours no connection to nextcloud possible anymore trough browser.
When trying to connect with local IP address i get “… untrusted domain”
Server is up and running. Apache and pgsql ok.
ssh ok.

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

Steps to replicate it:

  1. connect NC using https://

The output of your Nextcloud log in Admin > Logging:

don't know where to find

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

<?php
$CONFIG = array (
  'instanceid' => 'oc97vfin04v4',
  'passwordsalt' => 'AJZ3Dj/iGP66MUI6SZg7EwBISTgiCa',
  'secret' => 'B9VaXg8XRmQIoJZJX1Cnzi2udC1s6Qa8onGqpfkDEjqTbnD1',
  'trusted_domains' => 
  array (
    0 => 'localhost',
    1 => 'sld.tld',
    2 => 'sub.sld.tld',
  ),
  'datadirectory' => '/var/www/nextcloud/data',
  'dbtype' => 'pgsql',
  'version' => '21.0.0.18',
  'overwrite.cli.url' => 'https://sld.tld',
  'htaccess.RewriteBase' => '/',
  'dbname' => 'nextcloud',
  'dbhost' => 'localhost',
  'dbport' => '5432',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'user',
  'dbpassword' => 'password',
  'installed' => true,
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'mail_smtpmode' => 'smtp',
  'mail_smtpsecure' => 'ssl',
  'mail_sendmailmode' => 'smtp',
  'mail_smtphost' => 'provider',
  'mail_smtpport' => '465',
  'mail_smtpauth' => 1,
  'mail_smtpauthtype' => 'LOGIN',
  'mail_smtpname' => 'name',
  'mail_smtppassword' => 'password',
  'mail_from_address' => 'recipient',
  'mail_domain' => 'sld.tld',
  'default_language' => 'de_DE',
  'default_phone_region' => 'CH',
  'knowledgebaseenabled' => true,
  'maintenance' => false,
);

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

[Wed Mar 10 00:00:00.873605 2021] [mpm_event:notice] [pid 684:tid 548637271408] AH00489: Apache/2.4.38 (Debian) OpenSSL/1.1.1j configured -- resuming normal operations
[Wed Mar 10 00:00:00.873669 2021] [core:notice] [pid 684:tid 548637271408] AH00094: Command line: '/usr/sbin/apache2'
[Wed Mar 10 00:31:45.368034 2021] [mpm_event:notice] [pid 684:tid 548637271408] AH00491: caught SIGTERM, shutting down
[Wed Mar 10 00:32:40.996211 2021] [mpm_event:notice] [pid 713:tid 548269262192] AH00489: Apache/2.4.38 (Debian) OpenSSL/1.1.1j configured -- resuming normal operations
[Wed Mar 10 00:32:40.996580 2021] [core:notice] [pid 713:tid 548269262192] AH00094: Command line: '/usr/sbin/apache2'
[Wed Mar 10 00:37:10.186165 2021] [core:warn] [pid 713:tid 548269262192] AH00045: child process 715 still did not exit, sending a SIGTERM
[Wed Mar 10 00:37:12.188310 2021] [core:warn] [pid 713:tid 548269262192] AH00045: child process 715 still did not exit, sending a SIGTERM
[Wed Mar 10 00:37:14.190420 2021] [core:warn] [pid 713:tid 548269262192] AH00045: child process 715 still did not exit, sending a SIGTERM
[Wed Mar 10 00:37:16.192513 2021] [core:error] [pid 713:tid 548269262192] AH00046: child process 715 still did not exit, sending a SIGKILL
[Wed Mar 10 00:37:17.194239 2021] [mpm_event:notice] [pid 713:tid 548269262192] AH00491: caught SIGTERM, shutting down
[Wed Mar 10 00:38:10.902126 2021] [mpm_event:notice] [pid 703:tid 547612730736] AH00489: Apache/2.4.38 (Debian) OpenSSL/1.1.1j configured -- resuming normal operations
[Wed Mar 10 00:38:10.902462 2021] [core:notice] [pid 703:tid 547612730736] AH00094: Command line: '/usr/sbin/apache2'

I actually recognized my own public IP Address being banned by f2b. I will have to investigate how this happens. After unbanning all working again. sry for the incovenience.

To make your investigation easier, you could check what F2B jail had been used to ban your public IP. This is kind of a start to see why it got banned and go from there

1st case will be If you do not have any internal DNS (e.g. pihole) that pointed your FQDN to the LAN, then by typing yourDomain.com you will have an External IP Addrs as return. But you are in LAN… Here will apply NAT, rute and open Ports rules of your Modem/Ruter and messages will be forwarded to your LAN, but in the name of your EXTERNAL IP as host.

And if you have e.g. 3 LAN devices mistypes in a user name, for Nextcloud it will be = 1 IP addr that tries 3 user names with an error. Add your F2B rules and ban External IP addr.

thx guys

It was “nextcloud” jail banning my WAN IP. Probably one of my various clients has been the cause. Since having done some work on them i do not recognize additional “Found”-items on “/var/log/fail2ban.log”.

cheers

At least i know now it’s working :slight_smile: