Websocket server accessed over port 5240
Bug #1436279 reported by
Raphaël Badin
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Raphaël Badin | ||
1.8 |
Fix Released
|
Critical
|
Raphaël Badin |
Bug Description
My main MAAS testing machine only allows communication via port 80… when upgrading to the new MAAS version which uses Websocket, the UI was not working properly (see bug 1436277 for details).
We could maybe investigate the use of a module to have apache proxy the websockets connection: even if the plan is to drop apache in the future, people upgrading might still want to keep apache.
Related branches
lp:~rvb/maas/packaging-ws-tunnel
- Blake Rouse (community): Approve
-
Diff: 25 lines (+4/-0)2 files modifieddebian/changelog (+3/-0)
debian/maas-region-controller-min.postinst (+1/-0)
lp:~rvb/maas/tunnel-ws
- Blake Rouse (community): Approve
-
Diff: 159 lines (+26/-53)6 files modifiedcontrib/maas-http.conf (+1/-0)
src/maasserver/static/js/angular/factories/region.js (+9/-1)
src/maasserver/static/js/angular/factories/tests/test_region.js (+15/-0)
src/maasserver/templates/maasserver/index.html (+1/-1)
src/maasserver/views/index.py (+0/-11)
src/maasserver/views/tests/test_index.py (+0/-40)
lp:~rvb/maas/packaging-ws-tunnel-1.8
- Raphaël Badin (community): Approve
-
Diff: 25 lines (+4/-0)2 files modifieddebian/changelog (+3/-0)
debian/maas-region-controller-min.postinst (+1/-0)
lp:~rvb/maas/tunnel-ws-1.8
- Raphaël Badin (community): Approve
-
Diff: 159 lines (+26/-53)6 files modifiedcontrib/maas-http.conf (+1/-0)
src/maasserver/static/js/angular/factories/region.js (+9/-1)
src/maasserver/static/js/angular/factories/tests/test_region.js (+15/-0)
src/maasserver/templates/maasserver/index.html (+1/-1)
src/maasserver/views/index.py (+0/-11)
src/maasserver/views/tests/test_index.py (+0/-40)
Changed in maas: | |
milestone: | none → 1.8.1 |
milestone: | 1.8.1 → 1.9.0 |
Changed in maas: | |
assignee: | nobody → Raphaël Badin (rvb) |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Note, this is problematic when port forwarding through ssh.
Previously this worked:
$ ssh -L 8001:192. 168.64. 2:80 <email address hidden>
Then hitting http:// localhost: 8001
Now, you have to do: 168.64. 2:5240 -L 8001:192. 168.64. 2:80 ubuntu@ 10.245. 71.134 localhost: 8001
ssh -L 5240:192.
and hit http://
or 168.64. 2:5240 ubuntu@ 10.245. 71.134 localhost: 5240
ssh -L 5240:192.
and hit http://
Note, that
5240:<ip>:5240 is significantly less useful than ANYPORT:<ip>:80