Remote access is a route to the server you already own, and your library stays where it is; what changes is how you’ll reach it from outside the house. Quven gives you two ways in: a network path you manage yourself, free with the home experience, and a managed relay for when inbound networking isn’t available, or just isn’t worth the trouble.
Manage it yourself and you hold every control
A port forward, a reverse proxy or a private overlay network will expose your server without the relay ever entering the picture. Certificates, firewall, DNS, bandwidth: all of it is yours to decide, and yours to get right. That’s the route you want if you already run infrastructure at home and can judge the security boundary you end up with.
The native apps are where an address of your own gets typed. On the connect screen, Connect by address takes a bare host like 192.168.1.50 or a full https://quven.example.com, so whatever you’ve published is what goes in the field. The browser client at app.quven.tv works the other way round: it signs you in to your Quven Account, lists the servers linked to it and dials the one you pick over the relay. There’s no address field on that screen, and no amount of port forwarding will put one there.
The relay does the router work for you
NAT, carrier-grade NAT and a residential connection whose address moves every few days can make direct inbound access a losing battle. The relay lets linked clients reach your home server through Quven’s transport, and it won’t publish your server to the general internet to do it. The media still comes off your machine and still leaves through your uplink, so your home upload speed is still the ceiling.
It unlocks with Pro, and Max and Lifetime carry it too. The server itself has to be linked to that account, and until it is, the card says “Remote Access requires a linked Quven Account with Pro, Max, or Lifetime.” and the switch won’t move.
One thing you should know before choosing it, though. The relay terminates transport encryption today, which means it can see media while it forwards it. It’s built to keep no record of what passes through, but that’s a different promise from an opaque end-to-end tunnel, and the difference belongs in your decision.
Where the switch is, and what the card is telling you
Settings, then the Account tab. The Quven Cloud section holds a card called Remote access, with the toggle and two rows above it. It’s an administrator’s card, and everyone else gets a line saying so, which is also why nobody you’ve shared the server with can close your bridge.
State is the first row, and it reads Disabled, Connecting, Connected, Reconnecting or Failed, while Last heartbeat is the second, and it’ll only appear once the signalling channel has produced a healthy one, so a card that says Connected over a heartbeat from an hour ago is worth a second look. But Failed means the bridge didn’t open. Your server log names the reason, the server will try again on its next observation tick, and you should usually leave the switch on while it does.
Playing remotely can change the path your media takes
So will your upload cope? It and the bandwidth at the far end may force a lower bitrate even when the client understands the source codec perfectly well, and the only way to find out is to test the real thing on the real outside-LAN route: reconnect, seek, resume, and hold one transcode long enough for it to mean something. Logging in tells you the account works, and nothing more; whether the video arrives is a separate question.
Automatic quality follows what the connection actually sustains, and away from home that’s usually the answer you want. Choose a quality by hand and the relay will carry up to 2160p from Quven 1.1.4 onward; releases before that pinned a manual choice to 480p whatever the connection could do, which looked like a relay limit and was really a stale server default.
The Active streams card on the Activity tab is where an administrator watches a session as it plays, and there’s one label on it you should read carefully. A relayed request arrives at your server over loopback, so the chip on that session reads Local · 127.0.0.1. Remote on the same chip means something narrower: an address outside your own network reached the server directly, which is what your self-managed route looks like from the inside. If you want to know whether the bridge is up, that’s the Remote access card. This one will tell you what the server is doing with the file while somebody watches from a hotel.
Letting somebody else watch
You can share the whole server with people who have a Quven Account of their own, and you’ll do it at accounts.quven.tv. People lists who watches from your servers and which servers other people have shared with you. The invite itself goes out from the Servers section of the console, one server and one email address at a time.
And a guest signs in as themselves. Their watch state and their resume points are their own, and on your server they’re an ordinary user: no libraries, no settings, no remote-access switch. The seat count includes an invite nobody’s answered yet, so a pending invitation holds its place until it expires, and revoking access ends that guest’s sessions at once.
How many guests you can hold depends on your plan, and the plans page publishes the ceiling for each one. Sharing works on every tier, though your guest still has to be able to reach the machine, and the share card says so plainly where the invite is about to go: “Guests reach this server only where they can already meet it: on your own network, or through remote access you set up yourself. A Pro plan or higher adds the managed relay, which reaches it from anywhere.”
Host-local controls stay local. Update status, checks, downloads and installation happen on the host. Remote clients and the hosted web surface neither show those maintenance controls nor invoke them.
Frequently asked questions
Do I need the relay if I already forward a port?
No. The native apps reach a published address exactly as they reach a LAN one, and none of that traffic passes through anything of ours. What a port forward won’t give you is the browser client at app.quven.tv, which dials linked servers over the relay and won’t take an address.
Why does a remote session say Local in Active streams?
Because the relay hands the request to your server from the machine itself, and the chip reports the address the server saw. Over the relay that address is loopback. If you want the state of the bridge, that’s the Remote access card; Active streams will tell you what playback is doing.
Can somebody I share my server with change anything on it?
No. A guest authenticates as an ordinary user of that server, so nothing that administers it is open to them: libraries, scans, settings, the remote-access switch. Their watch state stays theirs as well, so their resume points won’t land on your profile.
The card says Failed. What should I check first?
The account and the plan, then the log. A relay that refuses a server now says which of the two is wrong instead of reporting the machine as offline, and you’ll find the failed bridge attempt logged with its reason on the server itself.