Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #11444 (closed)

Opened 11 years ago

Closed 11 years ago

RFE: Rethink the UI for changing server ports in Insight

Reported by: spli Owned by: jburel
Priority: minor Milestone: Unscheduled
Component: Insight Version: 4.4.8
Keywords: n.a. Cc: ux@…
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

  1. Setup an OMERO server to listen on non-standard ports (e.g. 14063/14064). Ensure no other servers on the same host are running on the standard ports (4063/4064).
  2. Launch Insight, in the server dialog enter the hostname and the port (14064).
  3. Attempt to connect, this should fail because Insight will use the default non-SSL port (4063) unless the lock icon in the login dialog is shown as locked, and by default it is unlocked.

Expected behaviour: Either changing the SSL port (14064) should automatically change the non-SSL port, or there should be the option to change both ports, or it should be made clear that only SSL connections are supported.

Change History (1)

comment:1 Changed 11 years ago by spli

  • Resolution set to invalid
  • Status changed from new to closed

As josh pointed out the server should tell the client which port to connect on. This fails if portforwarding (14063->4063, 14064->4064) is setup. Interestingly port-forwarding the same modified ports (14063->14063, 14064->14064) doesn't work either.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.75355 sec.)

We're Hiring!