Arch Linux User Repository

ngrok v3 introduces breaking changes.

Check https://ngrok.com/docs/guides/upgrade-v2-v3 for the upgrade instructions.

Note to self/future maintainers, this software only provides official downloads for an old release. The package itself then tries to update itself using 'equinox'. To find out the real download url, I use this script get_download_info:

#!/bin/bash

exec http -b https://update.equinox.io/check \
    'Accept:application/json; q=1; version=1; charset=utf-8' \
    'Content-Type:application/json; charset=utf-8' \
    app_id=app_goVRodbMVm \
    arch=amd64 \
    channel=stable \
    current_sha256=1aaccea9c0668d97f19095636b2f4fca033fb8d9f7fc37241a013f4f1fa48bb3 \
    current_version=2.2.8 \
    goarm= \
    os=linux \
    target_version= \
    "$@"

You need to call it with the different architectures:

get_download_info arch=386
get_download_info arch=amd64
get_download_info arch=arm
get_download_info arch=arm64

This is out of date, checksum needs to be updated. You can edit the PKGBUILD yourself during the install process and replace it (the field you want is probably sha256sums_x86_64). Right now the correct checksum is : 32d5cd63e47041931225d3a17dcd1d2d6a5a8f88f662cfe656e1d96e99af84bd If this doesn't work, go to https://ngrok.com/download, download the linux 64 bit archive and run sha256sum on the tarball.

Fails with: Validating source_x86_64 files with sha256sums... ngrok-stable-linux-amd64.zip ... FAILED ==> ERROR: One or more files did not pass the validity check!

Hi, would you consider adding support for armv7h too? It can be done using architecture specific downloads source_x86_64=("https://bin.equinox.io/c/4VmDzA7iaHb/ngrok-stable-linux-amd64.zip") sha256sums_x86_64=('0165a266388e80b467d6f97fcc42baa51da262c467b99bfb79305d7b6dd22b94') source_armv7h=("https://bin.equinox.io/c/4VmDzA7iaHb/ngrok-stable-linux-arm.zip") sha256sums_armv7h=('f2bf6e1c4221e7847a0c4fd3728f2140d7af80a8e0ab2072ae6c919d893bb254') (and also to fix so the package does work on 32 bit platform as it says it does with i686) source_i686=("https://bin.equinox.io/c/4VmDzA7iaHb/ngrok-stable-linux-386.zip") sha256sums_i686=('97746f160088a8fffd79a3897225b58ba62a1bb72cbbcce1d3542a786622fba6') Let me know if there is any problem adding this. Thanks, /Thomas

The checksum validation currently fails as the source URL points to an updated version of the binary archive. The current version is 2.1.18 and the correct SHA256 checksum value is: 0165a266388e80b467d6f97fcc42baa51da262c467b99bfb79305d7b6dd22b94.

please mark it as conflicting with previous ngrok-bin

This package is now based on ngrok 2.x, and is binary only. There is some auto-updating functionality built into ngrok now, but as I only recently switched to 2.x, I am not sure what effect this will have on the packaging. Please let me know if you run into any problems.

The package is broken because code.google no longer exists. It has been fixed upstream at https://github.com/inconshreveable/ngrok/pull/308 but not yet integrated into a release. I have asked to make a 1.7.2 version (https://github.com/inconshreveable/ngrok/issues/368) but in the meantime, if you want to build it, you need to modify the PKGBUILD. -source=("git+https://github.com/inconshreveable/ngrok.git#tag=${pkgver}") +source=("git+https://github.com/inconshreveable/ngrok.git")

I got an error on build(). Using Antergos: ==> Starting build()... go fmt ngrok/... go get github.com/jteeuwen/go-bindata GOOS="" GOARCH="" go install github.com/jteeuwen/go-bindata/go-bindata bin/go-bindata -nomemcopy -pkg=assets -tags=release \ -debug=false \ -o=src/ngrok/client/assets/assets_release.go \ assets/client/... go get github.com/jteeuwen/go-bindata GOOS="" GOARCH="" go install github.com/jteeuwen/go-bindata/go-bindata bin/go-bindata -nomemcopy -pkg=assets -tags=release \ -debug=false \ -o=src/ngrok/server/assets/assets_release.go \ assets/server/... go get -tags 'release' -d -v ngrok/... github.com/inconshreveable/go-update (download) package github.com/inconshreveable/go-update/check: cannot find package "github.com/inconshreveable/go-update/check" in any of: /usr/lib/go/src/github.com/inconshreveable/go-update/check (from $GOROOT) /tmp/yaourt-tmp-brad/aur-ngrok/src/ngrok/src/github.com/inconshreveable/go-update/check (from $GOPATH) github.com/inconshreveable/mousetrap (download) github.com/rcrowley/go-metrics (download) Fetching https://gopkg.in/yaml.v1?go-get=1 Parsing meta tags from https://gopkg.in/yaml.v1?go-get=1 (status code 200) get "gopkg.in/yaml.v1": found meta tag main.metaImport{Prefix:"gopkg.in/yaml.v1", VCS:"git", RepoRoot:"https://gopkg.in/yaml.v1"} at https://gopkg.in/yaml.v1?go-get=1 gopkg.in/yaml.v1 (download) github.com/inconshreveable/go-vhost (download) package code.google.com/p/log4go: unable to detect version control system for code.google.com/ path github.com/nsf/termbox-go (download) github.com/mattn/go-runewidth (download) github.com/gorilla/websocket (download) Makefile:8: recipe for target 'deps' failed make: *** [deps] Error 1 ==> ERROR: A failure occurred in build(). Aborting...

@neersighted ngrok-bin is ngrok 2.0 so I would say leave this package as-is.

I'm not sure how to go about updating to ngrok 2.0. It is a closed-source, totally different program. I'd like to keep this package (and ngrok-git) around. Does anyone object to a ngrok2 package?