Before you begin
Update to Shinphony 1.0.1 or later from the App Store to use Web preview. You need reachable SSH with TCP forwarding permitted, and an HTTP site reachable from that server. Shinphony does not create access to an otherwise unreachable home network.
Check the website from your SSH server
A development site on the same server might be
http://127.0.0.1:3000; another LAN machine might behttp://192.168.1.20:3000. These are examples. Verify that the SSH server can reach the chosen address. Another LAN machine needs an appropriate private-network listener and firewall rules, not a new public web port.Connect and open Web
Open your saved server. In the workspace navigation menu, choose Web, enter the development URL, and press Open. Older versions may show Web beside Terminal, Files and Git. Existing SSH credentials and host-key checks apply. If your own frp endpoint or jump host already provides SSH access, preview uses that SSH route.
Preview inside the app
localhostmeans the SSH server, not your phone. Back, Forward and Refresh work inside the preview. A detected HTTP link in Terminal also offers Preview via SSH. Choose that instead of Open in Browser for a URL reachable only from the server network.Reconnect or close
After a network change or iOS background suspension, choose Reconnect if needed. In Preview actions choose Disconnect (called Close preview in older interfaces) to end the preview session. This is not a VPN, an always-on tunnel or a full browser proxy.
A complete remote workflow
Preview a private development page, send a screenshot to your remote tool, then set up task notifications. Check each guide’s version and Pro requirements.
If something gets in the way
Web or Preview via SSH is missing
Check your version: these actions require 1.0.1 or later. Update from the App Store if you are still using 1.0. HTTPS links do not offer HTTP preview.
SSH connects but the page does not
Check the web port, bind address, firewall and SSH forwarding policy. Ask the administrator to permit the specific destination rather than broadly disabling protections.
How can I distinguish a website problem from a tunnel problem?
From the remote Terminal, run <code>curl -I --max-time 10 http://127.0.0.1:3000/</code> with your actual address. If it cannot connect there, check the web service first. A 405 response can simply mean the service rejects HEAD; try loading the page normally. If it works remotely but not in Web, check SSH forwarding and the selected origin.
Assets, login or live reload fail
Only the selected origin is forwarded. Other-host/port URLs, OAuth redirects and hardcoded WebSocket addresses may need dev-server changes. External subresources use the device network. The original remote Host header is not preserved, which affects virtual-host setups.
Can I preview HTTPS?
Not yet. HTTPS input is rejected rather than bypassing certificate checks. Open in Browser is separate and still requires normal device-network access.