No longer able to log into or sync with Nextcloud Server

The Basics

  • Nextcloud Server version = 30.0.4snap1 (45728)
  • Operating system and version = Ubuntu Mate 24.04.1
  • Web server and version (e.g, Apache 2.4.25): Whatever is in the Snap
  • Reverse proxy and version (e.g. nginx 1.27.2): Whatever is in the Snap
  • PHP version (e.g, 8.3): Whatever is in the Snap
  • Is this the first time you’ve seen this error? (Yes / No): Yes
  • When did this problem seem to first start? First noticed it yesterday 02Jan25. Log screen errors go back as far as 30Dec24.
  • Installation method = Snap
  • Are you using Cloudflare, mod_security, or similar? = No

Summary of the issue you are facing:

I am no longer able to access the web interface for Nextcloud from other machines, or sync devices. My setup has not changed, other than updates, for a couple of years and has worked fine until now. Attempting to load the WebUI from other machines presents a “Connection has timed out” error. Attempting to sync my calendars with various devices (via DavX5) fails silently. The only way to access the WebUI or sync with CalDAV is on the local machine (CalDAV syncing to local instance of Thunderbird).

Summary:
Local (server) Machine -

  • WebGUI via 127.0.0.1 = works
  • WebGUI via 192.168.1.233 = works
  • WebGUI via nextcloud.local = broken
  • CalDAV via Thunderbird = works

Syncing Devices-

  • WebGUI via 192.168.1.233 = broken
  • WebGUI via nextcloud.local = broken
  • CalDAV via DavX5 = broken
  • Nextcloud App = broken

Log entries

Nextcloud

I have a very long list of errors in my Administration settings->Logging screen. A large number appear to relate to mail server authentication issues and thinking it might have something to do with Microsoft changing the way Outlook mail works (and now causing my Live.com email to stop working), I deleted all mail settings with no change. Below I have picked out some more relevant entries, all of which appear several times each in the list.


|Error|richdocuments|ConnectException

cURL error 7: Failed to connect to 192.168.1.233 port 80: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://192.168.1.233/extra-apps/richdocumentscode/proxy.php?req=/hosting/discovery

Failed to fetch discovery: cURL error 7: Failed to connect to 192.168.1.233 port 80: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://192.168.1.233/extra-apps/richdocumentscode/proxy.php?req=/hosting/discovery

Raw:

{"reqId":"MtyFAeC9v7Qc0zbd6b1a","level":3,"time":"2025-01-03T01:44:39+00:00","remoteAddr":"","user":"--","app":"richdocuments","method":"","url":"--","message":"Failed to fetch discovery: cURL error 7: Failed to connect to 192.168.1.233 port 80: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://192.168.1.233/extra-apps/richdocumentscode/proxy.php?req=/hosting/discovery","userAgent":"--","version":"30.0.4.1","exception":{"Exception":"GuzzleHttp\\Exception\\ConnectException","Message":"cURL error 7: Failed to connect to 192.168.1.233 port 80: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://192.168.1.233/extra-apps/richdocumentscode/proxy.php?req=/hosting/discovery","Code":0,"Trace":[{"file":"/snap/nextcloud/45728/htdocs/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php","line":158,"function":"createRejection","class":"GuzzleHttp\\Handler\\CurlFactory","type":"::","args":["*** sensitive parameters replaced ***"]},{"file":"/snap/nextcloud/45728/htdocs/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php","line":110,"function":"finishError","class":"GuzzleHttp\\Handler\\CurlFactory","type":"::"},{"file":"/snap/nextcloud/45728/htdocs/3rdparty/guzzlehttp/guzzle/src/Handler/CurlHandler.php","line":47,"function":"finish","class":"GuzzleHttp\\Handler\\CurlFactory","type":"::"},{"file":"/snap/nextcloud/45728/htdocs/3rdparty/guzzlehttp/guzzle/src/Middleware.php","line":142,"function":"__invoke","class":"GuzzleHttp\\Handler\\CurlHandler","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/lib/private/Http/Client/DnsPinMiddleware.php","line":109,"function":"GuzzleHttp\\{closure}","class":"GuzzleHttp\\Middleware","type":"::","args":["*** sensitive parameters replaced ***"]},{"file":"/snap/nextcloud/45728/htdocs/3rdparty/guzzlehttp/guzzle/src/PrepareBodyMiddleware.php","line":35,"function":"OC\\Http\\Client\\{closure}","class":"OC\\Http\\Client\\DnsPinMiddleware","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/snap/nextcloud/45728/htdocs/3rdparty/guzzlehttp/guzzle/src/Middleware.php","line":31,"function":"__invoke","class":"GuzzleHttp\\PrepareBodyMiddleware","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/3rdparty/guzzlehttp/guzzle/src/RedirectMiddleware.php","line":71,"function":"GuzzleHttp\\{closure}","class":"GuzzleHttp\\Middleware","type":"::","args":["*** sensitive parameters replaced ***"]},{"file":"/snap/nextcloud/45728/htdocs/3rdparty/guzzlehttp/guzzle/src/Middleware.php","line":66,"function":"__invoke","class":"GuzzleHttp\\RedirectMiddleware","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/3rdparty/guzzlehttp/guzzle/src/HandlerStack.php","line":75,"function":"GuzzleHttp\\{closure}","class":"GuzzleHttp\\Middleware","type":"::","args":["*** sensitive parameters replaced ***"]},{"file":"/snap/nextcloud/45728/htdocs/3rdparty/guzzlehttp/guzzle/src/Client.php","line":333,"function":"__invoke","class":"GuzzleHttp\\HandlerStack","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/3rdparty/guzzlehttp/guzzle/src/Client.php","line":169,"function":"transfer","class":"GuzzleHttp\\Client","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/3rdparty/guzzlehttp/guzzle/src/Client.php","line":189,"function":"requestAsync","class":"GuzzleHttp\\Client","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/snap/nextcloud/45728/htdocs/lib/private/Http/Client/Client.php","line":205,"function":"request","class":"GuzzleHttp\\Client","type":"->"},{"file":"/var/snap/nextcloud/45728/nextcloud/extra-apps/richdocuments/lib/Service/DiscoveryService.php","line":59,"function":"get","class":"OC\\Http\\Client\\Client","type":"->","args":["*** sensitive parameters replaced ***"]},{"file":"/var/snap/nextcloud/45728/nextcloud/extra-apps/richdocuments/lib/Service/CachedRequestService.php","line":74,"function":"sendRequest","class":"OCA\\Richdocuments\\Service\\DiscoveryService","type":"->"},{"file":"/var/snap/nextcloud/45728/nextcloud/extra-apps/richdocuments/lib/Backgroundjobs/ObtainCapabilities.php","line":41,"function":"fetch","class":"OCA\\Richdocuments\\Service\\CachedRequestService","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/lib/public/BackgroundJob/Job.php","line":61,"function":"run","class":"OCA\\Richdocuments\\Backgroundjobs\\ObtainCapabilities","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/lib/public/BackgroundJob/TimedJob.php","line":88,"function":"start","class":"OCP\\BackgroundJob\\Job","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/lib/public/BackgroundJob/TimedJob.php","line":75,"function":"start","class":"OCP\\BackgroundJob\\TimedJob","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/cron.php","line":162,"function":"execute","class":"OCP\\BackgroundJob\\TimedJob","type":"->"}],"File":"/snap/nextcloud/45728/htdocs/3rdparty/guzzlehttp/guzzle/src/Handler/CurlFactory.php","Line":210,"message":"Failed to fetch discovery: cURL error 7: Failed to connect to 192.168.1.233 port 80: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://192.168.1.233/extra-apps/richdocumentscode/proxy.php?req=/hosting/discovery","exception":[],"CustomMessage":"Failed to fetch discovery: cURL error 7: Failed to connect to 192.168.1.233 port 80: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://192.168.1.233/extra-apps/richdocumentscode/proxy.php?req=/hosting/discovery"},"id":"67774cf41234b"}

|Error|no app in context|InvalidArgumentException

URL is missing scheme or host

Exception running check OCA\Settings\SetupChecks\WellKnownUrls: URL is missing scheme or host

Raw:

{"reqId":"LpcuUpktryTPTnFcaY7q","level":3,"time":"2025-01-02T08:00:31+00:00","remoteAddr":"127.0.0.1","user":"nextcloudadmin","app":"no app in context","method":"GET","url":"/index.php/settings/ajax/checksetup","message":"Exception running check OCA\\Settings\\SetupChecks\\WellKnownUrls: URL is missing scheme or host","userAgent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:133.0) Gecko/20100101 Firefox/133.0","version":"30.0.4.1","exception":{"Exception":"InvalidArgumentException","Message":"URL is missing scheme or host","Code":0,"Trace":[{"file":"/snap/nextcloud/45728/htdocs/apps/settings/lib/SetupChecks/CheckServerResponseTrait.php","line":61,"function":"normalizeUrl","class":"OCA\\Settings\\SetupChecks\\WellKnownUrls","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/apps/settings/lib/SetupChecks/CheckServerResponseTrait.php","line":130,"function":"getTestUrls","class":"OCA\\Settings\\SetupChecks\\WellKnownUrls","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/apps/settings/lib/SetupChecks/WellKnownUrls.php","line":56,"function":"runRequest","class":"OCA\\Settings\\SetupChecks\\WellKnownUrls","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/lib/private/SetupCheck/SetupCheckManager.php","line":34,"function":"run","class":"OCA\\Settings\\SetupChecks\\WellKnownUrls","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/apps/settings/lib/Controller/CheckSetupController.php","line":147,"function":"runAll","class":"OC\\SetupCheck\\SetupCheckManager","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/lib/private/AppFramework/Http/Dispatcher.php","line":208,"function":"check","class":"OCA\\Settings\\Controller\\CheckSetupController","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/lib/private/AppFramework/Http/Dispatcher.php","line":114,"function":"executeController","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/lib/private/AppFramework/App.php","line":161,"function":"dispatch","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/lib/private/Route/Router.php","line":302,"function":"main","class":"OC\\AppFramework\\App","type":"::"},{"file":"/snap/nextcloud/45728/htdocs/lib/base.php","line":1003,"function":"match","class":"OC\\Route\\Router","type":"->"},{"file":"/snap/nextcloud/45728/htdocs/index.php","line":24,"function":"handleRequest","class":"OC","type":"::"}],"File":"/snap/nextcloud/45728/htdocs/apps/settings/lib/SetupChecks/CheckServerResponseTrait.php","Line":97,"message":"Exception running check OCA\\Settings\\SetupChecks\\WellKnownUrls: URL is missing scheme or host","exception":[],"CustomMessage":"Exception running check OCA\\Settings\\SetupChecks\\WellKnownUrls: URL is missing scheme or host"},"id":"67774cf412b87"}

|Error|PHP

Trying to access array offset on value of type null at /var/snap/nextcloud/45728/nextcloud/extra-apps/richdocuments/lib/Service/CachedRequestService.php#146 

Raw:

{"reqId":"QLblC4UnceljrPhdPYmh","level":3,"time":"2024-12-30T02:32:44+00:00","remoteAddr":"","user":"--","app":"PHP","method":"","url":"--","message":"Trying to access array offset on value of type null at /var/snap/nextcloud/45728/nextcloud/extra-apps/richdocuments/lib/Service/CachedRequestService.php#146","userAgent":"--","version":"30.0.4.1","data":{"app":"PHP"},"id":"67774cf4133d4"}

Configuration

Nextcloud

The contents of my config.php file:

<?php
$CONFIG = array (
  'apps_paths' => 
  array (
    0 => 
    array (
      'path' => '/snap/nextcloud/current/htdocs/apps',
      'url' => '/apps',
      'writable' => false,
    ),
    1 => 
    array (
      'path' => '/var/snap/nextcloud/current/nextcloud/extra-apps',
      'url' => '/extra-apps',
      'writable' => true,
    ),
  ),
  'supportedDatabases' => 
  array (
    0 => 'mysql',
  ),
  'memcache.locking' => '\\OC\\Memcache\\Redis',
  'memcache.local' => '\\OC\\Memcache\\Redis',
  'redis' => 
  array (
    'host' => '/tmp/sockets/redis.sock',
    'port' => 0,
  ),
  'log_type' => 'file',
  'logfile' => '/var/snap/nextcloud/current/logs/nextcloud.log',
  'logfilemode' => 416,
  'instanceid' => 'oc2bh0h2dj0i',
  'passwordsalt' => '***redacted***',
  'secret' => '***redacted***',
  'trusted_domains' => 
  array (
    0 => '192.168.1.233',
    1 => 'nextcloud.local',
  ),
  'datadirectory' => '/var/snap/nextcloud/common/nextcloud/data',
  'dbtype' => 'mysql',
  'version' => '30.0.4.1',
  'overwrite.cli.url' => 'https://192.168.1.233',
  'dbname' => 'nextcloud',
  'dbhost' => 'localhost:/tmp/sockets/mysql.sock',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'nextcloud',
  'dbpassword' => '***redacted***',
  'installed' => true,
  'maintenance' => false,
  'app.mail.transport' => 'php-mail',
  'loglevel' => 2,
  'theme' => '',
  'maintenance_window_start' => 1,
);

@Heath3827 this issue is known Release 30.0.4snap1 by pachulo ¡ Pull Request #2999 ¡ nextcloud-snap/nextcloud-snap ¡ GitHub and there is no solution yet.

uninstall richdocumentscode until this issue has been addressed, see FAQ's ¡ nextcloud-snap/nextcloud-snap Wiki ¡ GitHub

disable third party app

   sudo nextcloud.occ app:disable richdocumentscode

or remove third party app

   sudo nextcloud.occ app:remove richdocumentscode

please consider creating an issue on the developers GitHub Issues ¡ CollaboraOnline/richdocumentscode ¡ GitHub

or workaround
How to install and configure Collabora CODE server for Nextcloud snap with docker

your syncing should work after the app has been removed. restart the snap sudo snap restart nextcloud after removing the app to be sure.

you could also revert to the previous version and hold refreshes see Managing Nextcloud snap but you’ll be missing out on automatic updates until you unhold.

see PHP configuration options especially setting trusted domains

1 Like

Hello,

Is your site only accessed internally, via 192.168.1.233 and this is your local LAN from which all other devices connect?

nextcloud.local is a local internal domain the syncing clients can resolve?
Is this DNS hosted on the same host as Nextcloud or another?

Is your server able to connect to the internet, receive updates, etc?

According to the github snap includes only the following components:

  • Nextcloud 30
  • Apache 2.4
  • PHP 8.2
  • MySQL 8.0
  • Redis 7.2

Have you checked the host to see if any new firewall settings have been created that would be blocking port 80 inbound? It would appear that apache is running as you can access it from the localhost but the remote clients cannot.

Your config.php trusted domains have your server IP and local domain which is needed.

I didn’t see the entries below in your config.php - I’m new to Nextcloud but these are part of the standard configurations I’ve seen so far:
‘overwritehost’ => ‘yourdomain.com’,
‘overwriteprotocol’ => ‘https’, (or HTTP if not using https)

You’ll want to check the well known configuration in apache - I’m using AIO so my installation is currently a little different but an example is:

<VirtualHost *:80>
ServerName yourdomain.com

# Redirect /.well-known to appropriate NextCloud endpoints
Redirect 301 /.well-known/carddav /nextcloud/remote.php/dav
Redirect 301 /.well-known/caldav /nextcloud/remote.php/dav

# General redirect for OpenID Connect or other services
Redirect 301 /.well-known/openid-configuration /index.php/.well-known/openid-configuration

DocumentRoot /var/www/html

When you access your admin interface for nextcloud and go to the office tab is your collabora server reachable and is it using the correct URL?

In responce to gp3:

Is your site only accessed internally, via 192.168.1.233 and this is your local LAN from which all other devices connect?
nextcloud.local is a local internal domain the syncing clients can resolve?
Is this DNS hosted on the same host as Nextcloud or another?

Yes, I only access Nextcloud on the LAN and it is not exposed to the internet. The domain name has been resolvable in the past. As for a DNS host, I haven’t set up my own DNS resolver but fileserver.local still resolves to my file server so that still works.

Is your server able to connect to the internet, receive updates, etc?

Yes.

‘overwritehost’ => ‘yourdomain.com’,
‘overwriteprotocol’ => ‘https’, (or HTTP if not using https)

I haven’t removed these entries, so if they aren’t there, they must be new variables that updates haven’t added. I have just added them manually with no change.

You’ll want to check the well known configuration in apache

I don’t know what this is or how to check it.

When you access your admin interface for nextcloud and go to the office tab is your collabora server reachable and is it using the correct URL?

I don’t have an Office ‘tab’. I have Nextcloud Office in the side bar and there is no mention of a Collabora server. I haven’t configured Nextcloud to enable office so that might be why.

Have you checked the host to see if any new firewall settings have been created that would be blocking port 80 inbound?

I did some looking and found iptables is enabled on my system. As I have recently added Tailscale to this machine I disabled it and suddenly everything started working (except nextcloud.local). So it appears enabling Tailscale is doing something to block incoming traffic? This is the difference in iptables:

Tailscale enabled=

sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
ts-input   all  --  anywhere             anywhere            

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         
ts-forward  all  --  anywhere             anywhere            

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

Chain ts-forward (1 references)
target     prot opt source               destination         
MARK       all  --  anywhere             anywhere             MARK xset 0x40000/0xff0000
ACCEPT     all  --  anywhere             anywhere             mark match 0x40000/0xff0000
DROP       all  --  100.64.0.0/10        anywhere            
ACCEPT     all  --  anywhere             anywhere            

Chain ts-input (1 references)
target     prot opt source               destination         
ACCEPT     all  --  Server-A             anywhere            
RETURN     all  --  100.115.92.0/23      anywhere            
DROP       all  --  100.64.0.0/10        anywhere            
ACCEPT     all  --  anywhere             anywhere            
ACCEPT     udp  --  anywhere             anywhere             udp dpt:41641
sudo iptables -S
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-N ts-forward
-N ts-input
-A INPUT -j ts-input
-A FORWARD -j ts-forward
-A ts-forward -i tailscale0 -j MARK --set-xmark 0x40000/0xff0000
-A ts-forward -m mark --mark 0x40000/0xff0000 -j ACCEPT
-A ts-forward -s 100.64.0.0/10 -o tailscale0 -j DROP
-A ts-forward -o tailscale0 -j ACCEPT
-A ts-input -s MYTAILNETIP/32 -i lo -j ACCEPT
-A ts-input -s 100.115.92.0/23 ! -i tailscale0 -j RETURN
-A ts-input -s 100.64.0.0/10 ! -i tailscale0 -j DROP
-A ts-input -i tailscale0 -j ACCEPT
-A ts-input -p udp -m udp --dport 41641 -j ACCEPT

Tailscale disabled =

sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination   

I disabled richdocumentscode with no change. I believe I need to find out how Tailscale is messing with the firewall.

Glad to see you found the source of the blockage.

By default tailscale is block all not expressly permitted so you will want to take a look at the tail scale config and allow local lan access to your tail scale client (your Nextcloud server). Look for the exit node configuration (–exit-node-allow-lan-access) as well as acl to enable concurrent access from the LAN and via tailscale while it’s active.

The --exit-node-allow-lan-access flag is only for clients and not exit nodes (it complained when I added the flag). I have Tailscale on this machine to act as my entry point into my network as it is always on. For good measure, I also tried --netfilter-mode=off with no change. I found a post on the Tailscale forum from someone with the same issue (unable to access their Unraid WebGUI) but has had no response for 2 years. I had a quick look at the ACL page, and the full screen of Java/json or whatever it is made my vision fuzzy - I don’t know what I’m looking at.

My Tailscale up command is currently sudo tailscale up --advertise-exit-node --advertise-routes=192.168.1.0/24 --accept-routes.

Thanks for the update.

To prevent tailscale from routing all traffic through its interface try the following:

sudo tailscale up --advertise-exit-node --advertise-routes=192.168.1.0/24 --accept-routes --snat-subnet-routes=false

You can also try this to allow the local server access to local resources.

sudo tailscale up --advertise-exit-node --advertise-routes=192.168.1.0/24 --accept-routes --exit-node-allow-lan-access

If your local firewall is blocking traffic while tailscale is active try the following.

Allow traffic from the LAN subnet

sudo iptables -A INPUT -s 192.168.1.0/24 -j ACCEPT

Allow forwarding between LAN and Tailscale

sudo iptables -A FORWARD -i tailscale0 -o eth0 -j ACCEPT
sudo iptables -A FORWARD -i eth0 -o tailscale0 -j ACCEPT

Unfortunatelly none of your suggestions worked :sleepy:

I compared the iptables -S output between the normal tailscale up and the one including exit note enablement and the output was the same as above. When I added the additional iptables configs as suggested, they look to be added prior to the extra lines by Tailscale. My understanding is iptables filters from top to bottom so will that mean any filters that negate a type of traffic will still affect it? That said, since the filter output is the same between no exit node and with exit node, will that mean it is Tailscale itself and not iptables intercepting the traffic and dropping it?

iptables with the suggested additional configs:

-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
-N ts-forward
-N ts-input
-A INPUT -j ts-input
-A INPUT -s 192.168.1.0/24 -j ACCEPT
-A FORWARD -j ts-forward
-A FORWARD -i tailscale0 -o eth0 -j ACCEPT
-A FORWARD -i eth0 -o tailscale0 -j ACCEPT
-A ts-forward -i tailscale0 -j MARK --set-xmark 0x40000/0xff0000
-A ts-forward -m mark --mark 0x40000/0xff0000 -j ACCEPT
-A ts-forward -s 100.64.0.0/10 -o tailscale0 -j DROP
-A ts-forward -o tailscale0 -j ACCEPT
-A ts-input -s 100.67.59.45/32 -i lo -j ACCEPT
-A ts-input -s 100.115.92.0/23 ! -i tailscale0 -j RETURN
-A ts-input -s 100.64.0.0/10 ! -i tailscale0 -j DROP
-A ts-input -i tailscale0 -j ACCEPT
-A ts-input -p udp -m udp --dport 41641 -j ACCEPT

Got some answers on Reddit (r/Tailscale). Turns out it was the --accept-routes flag that was causing all the issues. All I needed to run was sudo tailscale up --advertise-exit-node --advertise-routes=192.168.1.0/24 .

Thankyou all who helped to find my solution.

Glad to hear - was going to mention routing again, glad you got it solved and posted the solution!

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.