I have been attempting to do a fresh install of Discourse on a fresh installation of Ubuntu Server 16.04 but the installation fails during bootstrapping. The launcher downloads the Discourse image successfully but fails when attempting to access ‘ GitHub - discourse/pups: Simple yaml based bootstrap…

Well it turns out the issue was in fact the MTU of the docker0 network adapter. I resolved the issue by changing the following line: ExecStart=/usr/bin/dockerd -H fd:// to ExecStart=/usr/bin/dockerd --mtu=1400 -H fd:// in my /lib/systemd/system/docker.service Thanks for trying to assist.

Hi Sisko, I’m unable to reproduce this, on a fresh DO droplet running Ubuntu 16.04. Is there any chance you’re behind some sort of HTTPS proxy, or something else that could be getting in the way? If you’re quite sure your Internet connection is clean, could you do a full-packet capture of the TLS…

Hey Matt, I havent set up a proxy on my server but its possible that the host network is using one, i have contacted my host to check but i am still waiting on a reply. In the meantime i have run the packet capture you requested and will PM you the results shortly.

Hi Sisko, There’s definitely a proxy, or something else untoward, in the way. It’s dropped the first segment of the server’s response to the TLS handshake, leaving a corrupted session. Time to shake your ISP until some sense falls out – or just use DigitalOcean. We recommend them because this so…

Thanks! I will contact my server host again.

I have just heard back from my server host and they have told me there is no proxy setup on their network. There are no proxys setup on our network, if your running 1400 mtu the only other hinderance stopping it from working would be that their servers are in China or Russia which we are currently…

As this isn’t a Discourse problem, we can’t really help you. I’d suggest getting further assistance from your hosting provider, because the packet capture clearly shows something funky happening in the network.

My main question here is, COULD this issue be the MTU of the network adapter that Discourse is using (the docker interface)? Because if the issue COULD be with the MTU i can make further attempts to change it, if the issue CANT be the MTU then i can pressure my hosting provider further. They will …

The --mtu=1400 also helped me. The cause of my problem was a VPN. When running the docker without VPN it worked. Somehow VPN and other virtual environments may cause docker to lower the MTU

We’ve had a similar issue with a fresh install of Discourse on the UKCloud provider, which we haven’t used for Discourse before. The install or ./launcher rebuild app would fail when it tried to update the gems: FAILED -------------------- Pups::ExecError: cd /var/www/discourse && gem update bundle…

Frische Installation schlägt fehl - gnutls_handshake() failed: Fehler in der Pull-Funktion

Unterstützung Installation

mpalmer (Matt Palmer) 8. September 2016 um 04:34 11

I can’t help, and I can’t recommend anyone who could.

1 „Gefällt mir“

Thema		Antworten	Aufrufe
Trouble Rebuilding: gnutls_handshake() failed Self-hosting	1	841	7. September 2023
Help! gnutls_handshake() failed: Error in the pull function Self-hosting	1	1258	1. März 2021
My server can access github, but docker can't Self-hosting unsupported-install	2	1256	7. Juni 2023
Issue when installing new Discourse instance Self-hosting	7	1431	2. April 2023
Failed install on ubuntu 22.04 Self-hosting	1	1069	25. Dezember 2023

Frische Installation schlägt fehl - gnutls_handshake() failed: Fehler in der Pull-Funktion

Verwandte Themen