Troubleshooting¶
Checks for the Gradio failures the published getting-started page prepares you for.
The browser does not load the page¶
Cause: the port forward is not running, or it is pointed at another instance. The service listens on loopback port 7860.
Fix: wait until first boot has finished, start the forward, and open
http://127.0.0.1:7860 on the workstation:
aws ssm start-session --target <instance-id> \
--document-name AWS-StartPortForwardingSession \
--parameters '{"portNumber":["7860"],"localPortNumber":["7860"]}'
On the instance:
Sign-in is rejected¶
Cause: the username or password does not match
/home/ubuntu/.config/sushi-gradio/access.json on this instance.
Fix: as ubuntu, read the file in the session and enter those values in
the login page. Do not delete the file. First boot keeps the original
identity.
Predict rejects the text¶
Cause: the input is longer than 512 characters or 64 English words, or it does not include a word from the original examples.
Fix: use a short example that includes those words, such as
helpful excellent service or awful poor service.
sushi-gradio read cannot find the prediction¶
Cause: the output path was reused, or the JSON file is not the one
predict just wrote. Every prediction needs a new filename.
Fix: pick a new path under ~/gradio-results/ and run predict, then
read, on that path. See
Predict and check the result.
Predictions disappeared after a copy¶
Cause: the copy included only one of /var/lib/gradio, the access file,
and ~/gradio-results.
Fix: restore all three from the same backup, with ownership and modes preserved, then read an existing JSON file.
Last updated October 27, 2026 · Suggest an improvement