Remote access

Rerinku View runs on your own machine. On your home LAN, open its address in a browser and you’re ready to go. When you’re away from home, there are two options: turn on Quick Connect in Rerinku View, or expose it yourself with a reverse proxy or VPN.

LAN access

On first start, Rerinku View creates config.yaml in its working directory and listens on 0.0.0.0:8080 by default, so devices on the same network can open the console at http://<machine-ip>:8080. The Docker image also listens on port 8080 on all addresses.

If you only want to use it on this machine, change the listen address to 127.0.0.1:8080 (the environment variable HTTP_ADDR, or the matching entry in the config file).

Anyone on your LAN can open the console. Without an access password, devices on the same network can use the console without signing in, and can bind a phone directly. To keep others out, set an access password.

Quick Connect

Quick Connect lets you open your own Rerinku View from anywhere at a fixed HTTPS address. You don’t need a public IP, and you don’t need to change your router settings.

1. Open Settings → Quick Connect → Remote access and click Connect to Rerinku Cloud.
2. Your browser goes to rerinku.com. Sign in (create an account first if you don’t have one) and authorize this Rerinku View. Your password never passes through Rerinku View.
3. After you authorize, you’re taken back to the console automatically, and the page shows this Rerinku View’s Public address, which looks like https://n1234….nodes.rerinku.com.

How it works:

• Rerinku View opens an outbound encrypted tunnel to Rerinku Cloud, and requests from outside come in through the Cloud gateway. The gateway handles HTTPS, so the content of console pages, API calls, playback and thumbnails passes through the gateway.
• Live video doesn’t go through the tunnel. Live video travels directly between your browser and Rerinku View over WebRTC (encrypted with DTLS-SRTP). When the two sides can’t connect directly, it’s forwarded through Rerinku Cloud’s TURN relay.
• The public address itself is the way in: anyone who has the address can open your console. When Quick Connect is on, be sure to set an access password.

Managing it:

• The Enable Quick Connect switch lets you turn it off for a while. The configuration is kept, and you can turn it back on at any time.
• Disconnect and remove tells Rerinku Cloud to release this node and deletes the connection info on this machine. If Cloud can’t be reached at the moment, the info is still deleted, and you’re asked to remove the node manually in the Cloud console.
• If you revoke a Rerinku View in the Rerinku Cloud console, it stays in the Revoked by Cloud state. You need to Disconnect and remove it first, then connect again.

If you’d rather not use Cloud, you can expose Rerinku View yourself with a reverse proxy (such as Nginx or Caddy) or a VPN (such as WireGuard or Tailscale). When you access it through a reverse proxy, set TRUST_PROXY_HEADERS=true so Rerinku View recognizes the real client address and HTTPS.

Rerinku View phone app

The Rerinku View Android app lets you watch video, see events and get notifications on your phone. It needs Android 7.0 or later. Install it from the download page.

Pairing:

1. In the console, open Settings → Quick Connect → Phone app. The page shows a QR code.
2. Scan the QR code in the app and confirm to finish binding. The QR code only contains Rerinku View’s address, not a password. After binding, the app gets a long-lived token.
3. Bound phones are listed under Bound phones on the same page, and you can Unbind them at any time.

The addresses in the QR code are the address you currently have the console open at and this machine’s LAN IP. They don’t include the Quick Connect address. To use the app away from home too, change the server address in the app to the Quick Connect address. The app stores only one address per server and does not switch automatically between the LAN and Quick Connect.

What the app can do:

• Devices: live video. You can switch quality, turn sound on or off, go fullscreen, take screenshots, and save a stretch of recording to your phone’s photo gallery. Below the video are this camera’s recent events.
• Events: filter by All, People, Faces or Alarm input. Event details include a screenshot with the targets marked, and the event recording.
• Notifications: new events are pushed to your phone. Tap one to go straight to the matching live view or event details.

The app doesn’t support timeline playback, PTZ or talkback yet, and the iOS version isn’t in the App Store yet.

The current version of the app can’t bind to a Rerinku View that has an access password set (the app doesn’t have a password field yet). Phones that are already bound are not affected.

Push notifications

Rerinku View decides what each phone notification says and who gets it, writes the text in the phone’s language, and then sends it to the phone through the push relay at rerinku.com. The relay needs no account, and Quick Connect doesn’t need to be on. Rerinku View just needs internet access. Images in notifications don’t go through the relay: after the phone receives a notification, it uses its own token to fetch the image from Rerinku View.

The master switch and rules for notifications are under Settings → Notifications. See Events and notifications.

Access password

An access password is how you keep other people out. Set it under Settings → Sessions → Access password. It must be at least 8 characters.

Once an access password is set:

• Every browser must sign in first, including when the console is opened on this machine and when it’s accessed through Quick Connect. Sign-ins last 30 days and are renewed automatically whenever you use the console during that time.
• When you change or remove the password, every browser is signed out. Bound phones and Home Assistant are not affected.
• New bindings must provide the password. Repeated wrong attempts are rate-limited.
• If no access password is set and Rerinku View can be reached from outside (it listens on a LAN address, or Quick Connect is on), a notice appears at the top of the console.

Forgot the password: start Rerinku View once with the environment variable RESET_ACCESS_PASSWORD=1, and the password is cleared. Afterward, be sure to remove the variable and restart.

Authorized devices and apps

Where	What it manages
Settings → Quick Connect → Phone app → Bound phones	Phones and Home Assistant
Settings → Developer → Authorized apps	Third-party programs and read-only view tokens. See Open API

After you revoke access, their requests are rejected. Note: without an access password, unbinding only “disconnects” them, and they can bind again just by scanning the QR code.

What data leaves this machine

When	Sent to	Content
Always (on by default)	Rerinku Cloud	An installation report every 10 minutes: instance ID, version, operating system and a hardware summary. Set CLOUD_REPORT=false to turn it off
When there’s a notification to send	Push relay	Device name, event category (including the person’s name when a familiar face is recognized), push token and related IDs. No images
Once Quick Connect is on	Rerinku Cloud gateway	All HTTP content accessed through the Quick Connect address (pages, API, playback, thumbnails)

Camera video, recordings and recognition results are stored on this machine by default. See the Privacy Policy for details.