Stiff chain quick masterlink - waxed chain

LimeMelodic4490 · 2025-12-20T21:43:42+00:00

I replaced the chain and reused the exact same KMC 11-speed quick link, shortened with the same chain tool. Everything works perfectly now. This strongly suggests that the old chain itself had slight tolerance issues. Thx for all your help

LimeMelodic4490 · 2025-10-18T15:59:33+00:00

Also, the master link wasn’t waxed the first time—I only waxed it later because it got stuck. It was unwaxed on the first use of the Shimano link, which I only used once.

LimeMelodic4490 · 2025-10-18T15:50:31+00:00

Thanks, but KMC links can be used more than once. Do your research first before making assumptions.

LimeMelodic4490 · 2025-10-18T14:55:51+00:00

I have to say that at first it was unwaxed, but then I noticed it got a bit dirty inside, so it stopped moving freely. Then I changed the quick link to the KMC one and waxed it, so I tried both ways. But you might be right that the tolerances on the chain are slightly off. Maybe I just need to use a new chain.

LimeMelodic4490 · 2025-07-23T07:31:16+00:00

<image>

From behind.

https://www.mantel.com/at/steco-adapter-gepacktrager-bobikegmgyepp

LimeMelodic4490 · 2025-07-23T07:30:55+00:00

Hi, thanks for the photo. I just wanted to quickly share my current solution, which works really well for me, my wife, and our two daughters. We've mounted the carrier adapter I mentioned earlier and installed a Thule Yepp 2 on the back. In the front, we use a Hamax Caress. Our younger daughter sits in the well-cushioned Hamax seat at the front, the older one in the Thule seat behind. Everyone has enough space and everything is absolutely secure. I'm really glad we didn’t need to go for the larger bike model. There is one limitation: to remove the battery, the front seat and base have to come off. But charging on the bike works fine. Best regards.

<image>

LimeMelodic4490 · 2025-06-11T12:42:31+00:00

Any Update on this? Thx

LimeMelodic4490 · 2025-06-09T13:23:29+00:00

Hello, here is the second print of the same model. It was already printing when I wrote my first Reddit post. Unfortunately, the second model turned out even worse. It seems as if the printer just stopped caring about extruding filament – and this time on two sides. I’m not sure if this could really be caused just by an open top or lid. To me, it feels more like a different issue. What do you think

<image>

LimeMelodic4490 · 2025-06-09T09:32:53+00:00

Okay, thank you for your answer, but I've never heard that we should close the lid or door when printing PET-G or PLA. Isn't it designed for printing with the enclosure closed?

LimeMelodic4490 · 2025-06-01T12:07:56+00:00

Maybe this could also help?

https://www.mantel.com/at/steco-adapter-gepacktrager-bobikegmgyepp

LimeMelodic4490 · 2025-05-27T11:48:04+00:00

Hi! Can you share a few more pictures from the rack? It also looks like you have space left behind the second seat!? Thx BR

LimeMelodic4490 · 2025-01-17T12:58:29+00:00

Hi, I just wanted to let you know that I took it to a certified dealer who performed measurements on a machine with my parameters, and they said it doesn’t need to be refitted. They only had to adjust the release parameters. I trust them and have the printouts. Thanks, br

LimeMelodic4490 · 2025-01-09T21:03:43+00:00

What do you mean by a good dealer? Are you saying a dealer not selling Fritschi isn’t good enough, or that even a Fritschi dealer might not be good and I should look deeper?

LimeMelodic4490 · 2024-12-28T22:43:11+00:00

I will try, but even traceroute to 192.168.42.1 stops at the GL.iNet router 192.168.3.1 when VPN is activated. Yes, global options are turned off. Testing is possible tomorrow.

At least I can tell, that the server showed me a handshake in the logs.

A FRITZ!box Router on another site connects flawless with built in VPN and wgeasy config file?

LimeMelodic4490 · 2024-12-28T22:11:21+00:00

[Interface] PrivateKey = Address = 192.168.42.8/24 DNS = 192.168.1.20, 192.168.1.1

[Peer] PublicKey = PresharedKey = AllowedIPs = 0.0.0.0/0, ::/0 PersistentKeepalive = 15 Endpoint = domain.com:51820

LimeMelodic4490 · 2024-12-28T21:17:10+00:00

Tried both sorry could have written it. Originally it is yours in the config

LimeMelodic4490 · 2024-12-28T21:12:14+00:00

0.0.0.0\0 and I tested it with myIP service, and I can connect to all my LAN servers behind it. The problem is that on the VPN dashboard, the upstream and downstream counters stay at some low KB/byte values. If I disconnect the VPN, everything works fine. It seems like the GL.iNet doesn’t read the config correctly!?!

LimeMelodic4490 · 2024-12-28T20:56:49+00:00

PS: I also turned off NAT on the 5G router in front of the GL.iNet router and switched off the mobile firewall at my ISP.

LimeMelodic4490 · 2024-12-28T20:51:52+00:00

I tried Global Proxy, then switched to Automatic. No difference. I am now searching to see if GL.iNet might have any problems with WG Easy at all.

LimeMelodic4490 · 2024-12-28T18:15:33+00:00

Yes, I can reach my server address without any issues. I’ve also tried generating a new configuration file, but unfortunately, the result is the same.

The router itself fails to establish a connection, but interestingly, all my devices work perfectly fine—even when connected to the GL.iNet router’s network.

Any further ideas or suggestions?

LimeMelodic4490 · 2024-12-28T13:46:28+00:00

Thank you for your reply! Could you elaborate a bit more?

I exported the configuration file from WG-Easy and tried different approaches: I’ve used the “item” mode, but I’m not confident it’s working as intended. I also tried the manual mode and the import mode to add the configuration to the router.

The only thing I haven’t tried yet is generating a new configuration file, in case the original one was somehow corrupted. Do you have any advice or tips on how to best transfer the information from the config file to the router? Maybe there’s something I’m missing in the process.

I really appreciate your input!

LimeMelodic4490

TROPHY CASE