Device Unavailable
Device Unavailable (in Opera Unite) should mean that either you made a typo in address or the Opera browser that was serving the content is offline.
Unfortunately, right now, since current Opera release is alpha (i.e. prerelease) there are some bugs, particularly one that keeps disconnecting service from main servers. This would probably be fixed.
The workaround for your own services (for now) is to disable Unite and then enable it.
Opera Unite relies on user keeping the browser window open, then a visitor can access the files they share or the applications they run. If the browser is closed - this information is unavailable.
In some near future you can try to use Web Archive → or use Google's cache → to see whether the information was cached. It it was - you might be able to recover a part of it.
Last updated
- Markuper (HTML templates)
- .ua
- Opera Unite HowTo's
- .us (files)
- Distribute Your Application
- 24/7 sites (permanent applications - idea) [stub]
- Issues
- HTTP Connections (AJAX/REST)
- Cookies
- file_wrap.js - File Wrapper
- Basic HowTo: Simple app (tutorial)
- Static images, client-side scripts
- Application Examples
- How to Debug Opera Unite apps
- Persistence & databases
- Opera Unite benchmark
- From PHP to Opera Unite
- Uniteness (Framework)
- Config.xml
- Key-value storage
- Widget Object
- Notifications (Growl'esque)
- Reset (debug)
- Cron example
- What I meant by CNAMEs
- Wish List
- Device Unavailable
- StopLorem (Opera Unite blogging)
- uniteness-0.11
- GET/POST data
- CRUD And Static (example)
- Opera object
- URLs
- Headers & Redirects
- Error Console
- JSON State (storing data)
- Security
- /storage/ (in fileio)
- Yusef library
- unite_info (a-la php_info)
- Javascript Imports
- onunload / _close
- fileio: Sandboxed Filesystem
- Request Hierarchy (like php_info)
- Intro: Web Apps with Opera Unite