clmbmb

Update: I solved my problem. I got everything working by using this repo, but also by not using LibreWolf - looks like either I'm missing something about its setup, or syncstorage-rs (firefox sync) doesn't handle it well: I noticed that when using it I would get "ua.os.ver":"UNKNOWN" in the logs, so maybe it's related.

I'm trying to host my Firefox Sync server. I got it running using docker and with instructions from this github repo. Everything looks fine, I think... I can reach the host and I can reach the __heartbeat__ endpoint, getting this response: {"version":"0.13.6","quota":{"enabled":false,"size":0},"database":"Ok","status":"Ok"}, but nothing seems to sync!

I set it up first on my LibreWolf instance and checking the docker container logs look like this:

Oct 12 10:43:42.840 INFO Starting 1 workers
Oct 12 10:43:42.844 INFO Starting "actix-web-service-0.0.0.0:8000" service on 0.0.0.0:8000
Oct 12 10:43:42.844 INFO Server running on http://0.0.0.0:8000 (mysql) No quota
Oct 12 10:43:59.438 INFO {"ua.os.ver":"NT 10.0","ua.name":"Firefox","ua.browser.family":"Firefox","uri.method":"GET","ua.os.family":"Windows","uri.path":"/__heartbeat__","ua.browser.ver":"130.0","ua":"130.0"}
Oct 12 10:43:59.706 INFO {"ua.os.ver":"NT 10.0","ua":"130.0","ua.browser.ver":"130.0","ua.os.family":"Windows","uri.path":"/favicon.ico","ua.name":"Firefox","ua.browser.family":"Firefox","uri.method":"GET"}
Oct 12 10:44:11.178 INFO {"ua.browser.family":"Firefox","ua.browser.ver":"130.0","uri.method":"GET","uri.path":"/1.0/sync/1.5","ua.os.family":"Linux","token_type":"OAuth","ua.os.ver":"UNKNOWN","ua.name":"Firefox","ua":"130.0"}
Oct 12 10:44:11.540 INFO {"ua.name":"HTTP Library","ua.os.family":"Other","ua.browser.family":"Other","ua":"curl","uri.path":"/__heartbeat__","uri.method":"GET","ua.browser.ver":"curl","ua.os.ver":"UNKNOWN"}
Oct 12 10:44:11.756 INFO {"ua.os.ver":"UNKNOWN","uri.path":"/1.0/sync/1.5","ua":"130.0","uri.method":"GET","token_type":"OAuth","ua.browser.ver":"130.0","ua.browser.family":"Firefox","ua.name":"Firefox","first_seen_at":"1728729851747","metrics_uid":"fcdfa197568a554e5f5b0a2d05d7b674","ua.os.family":"Linux","uid":"fcdfa197568a554e5f5b0a2d05d7b67452c597ab6caf7770a423378f86d1a4c0"}

I set my sync settings to have add-ons, bookmarks and history synced. I installed some add-ons, saved some bookmarks and tried to sync with a new browser profile, then with Firefox on Fedora and Mull on Android, but nothing seems to be moving.

Any idea what more to do to troubleshoot this?

I have a pi hole in my network and I set it as my primary DNS server, and my router (a Mikrotik) as secondary. DHCP sets the DNS servers as pihole, mikrotik in this exact order and I want to keep it that way. I know systemd-resolved uses some algorithm to set the fastest dns as current server, but I don't want/need that. Is there some way to do configure it to just let it be?

I'm running Fedora 40.

I'm trying to move away from cron jobs, not that they don't work, but I want to get on with the times and also learn some things.

I created two user timers (and the associated services), one for backing up my data and the second to upload to B2. I'm using two scripts I had in my cron jobs for a few years and they worked without problems. But with systemd timers both scripts fail with exit code 15 (process terminated) and I have no idea why.

I run Debian 12 Bookworm.

Here's the output for the status of the upload service:

> systemctl --user status rclone-up.service
○ rclone-up.service - Run rclone up for b2
     Loaded: loaded (/home/clmbmb/.config/systemd/user/rclone-up.service; disabled; preset: enabled)
     Active: inactive (dead)
TriggeredBy: ● rclone-up.timer

Apr 11 06:10:39 tesla systemd[1698218]: Starting rclone-up.service - Run rclone up for b2...
Apr 11 06:12:18 tesla systemd[1698218]: rclone-up.service: Main process exited, code=killed, status=15/TERM
Apr 11 06:12:18 tesla systemd[1698218]: rclone-up.service: Failed with result 'signal'.
Apr 11 06:12:18 tesla systemd[1698218]: Stopped rclone-up.service - Run rclone up for b2.
Apr 11 06:12:18 tesla systemd[1698218]: rclone-up.service: Consumed 12.811s CPU time.

Also, here's the log created by rclone while running:

2024/04/11 06:10:42 INFO  : integrity.2376: Copied (new)
2024/04/11 06:10:43 INFO  : hints.2376: Copied (new)
2024/04/11 06:10:43 INFO  : nonce: Copied (replaced existing)
2024/04/11 06:10:47 INFO  : config: Updated modification time in destination
2024/04/11 06:10:55 INFO  : index.2376: Copied (new)
2024/04/11 06:11:40 INFO  :
Transferred:      443.104 MiB / 2.361 GiB, 18%, 16.475 MiB/s, ETA 1m59s
Checks:              1503 / 1503, 100%
Transferred:            4 / 19, 21%
Elapsed time:       1m0.8s
Transferring:
 *                                   data/2/2328: 19% /502.259Mi, 2.904Mi/s, 2m19s
 *                                   data/2/2329: 52% /500.732Mi, 10.758Mi/s, 22s
 *                                   data/2/2330: 14% /501.598Mi, 3.150Mi/s, 2m15s
 *                                   data/2/2331:  0% /500.090Mi, 0/s, -

2024/04/11 06:12:18 INFO  : Signal received: terminated

Where should I look to get some more information about what's going on? Why would the service be terminated like that?

LE:

Setting TimeoutSec=infinity inside the [Service] section of the unit file seems to help. Not 100% if it's a good idea, but I'll experiment with it.

So, at the moment I'm using Nginx Proxy Manager, but lately I started seeing it moving slower and slower and even though I tried traefik some time ago, I didn't manage to make it work.

Anyway, I want to start using traefik again, but I want to use it like this:

• I want to access all my services/containers in my LAN through http (port 80) on something like sub.mylan.home
• I want to access some of my services over the internet through https (port 443) on sub.mydomain.com

I know this is possible, but I don't get the hang of the configuration. Somone care to share some tips?

I've used wireguard for a pretty long time on my server and the phone as a client. I've had the same configuration for at least 4-5 years and never had issues. Last week I moved to using pihole in a container with a macvlan interface, so it has a different IP address than my physical server. Then I went and changed the DNS server IP on the wireguard config on the phone. When I reconnected I see I can't connect to any local IP address like I used to and I can't figure out why.

The local LAN is 10.11.12.0/24, the VPN is on 10.11.13.0/24.

Here's the server wireguard config:

[Interface]
Address = 10.11.13.1
ListenPort = 11194
PrivateKey = ...

PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o enp3s0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o enp3s0 -j MASQUERADE

[Peer]
# Galaxy S20+
PublicKey = U59JZqVbk2eFxTb7tteyu0WHlMTZsk68E7CF7v2AX2U=
AllowedIPs = 10.11.13.5/32

[Peer]
# narwhal - T480 job
PublicKey = Ja9OL13IoZA17GJq0/LbwizB9s2dRQLHHgW2C4TcFyY=
AllowedIPs = 10.11.13.7/32

And here's the phone's wireguard config:

Address = 10.11.13.5/24
DNS = 10.11.12.55
PrivateKey = ....

[Peer]
AllowedIPs = 10.11.0.0/16
Endpoint = my_dyndns_hostname:11194
PublicKey = 6aF1cJhH9oeQWr9LYOpH3wk+lN4k9/tSiAqV6LkUQ1Y=

I am able to connect and can ping 10.11.12.77, the IP address of the server, but nothing else. I have two RPis running as mpd servers and I used to be able to connect to them too, but not anymore. Their IP addresses are 10.11.12.105 and .106.

Also, before the dns change I was able (of course!) to use the local DNS I set up on the pihole, but now I'm not able to connect to the new DNS (.55) so I can't get any local address to resolve.

I'm looking for some hints on what I'm doing wrong. Please help.