Can access swagger-editor at 127.0.0.1:9000 but not at myhost.domain:9000

[David Biesack]

This worked when I last tried it a few weeks ago, but now I can only access swagger-editor via http://127.0.0.1:9000 , not by my actual desktop's fully qualified hostname (http://djb.na.sas.com:9000 on our intranet). Both Google Chrome and Firefox return errors such as 

     Google Chrome's connection attempt to djb.na.sas.com was rejected. The website may be down, or your network may not be properly configured.

I don't recall doing any network or other configuration changes. This is running on Linux (Ubuntu 14.10) 

Note: I recently did a full stop of npm/node processes, performed a 'git pull', 'grunt build' (successful) and restarted my swagger-editor with 'npm start'. again, running on 127.0.0.1:9000 works fine. Other services such as cors-it are running fine on my djb.na.sas.com (on other ports).

Has something changed recently with swagger-editor to restrict it to 127.0.0.1? I'd like other folks on our team to use swagger-editor that I'm running.

thanks,

djb

[Ron]

You should open an issue on swagger-editor regarding this.

--
You received this message because you are subscribed to the Google Groups "Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email to swagger-swaggers...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[David Biesack]

done: https://github.com/swagger-api/swagger-editor/issues/294 

[David Biesack]

I can update the hostname in https://github.com/swagger-api/swagger-editor/blob/master/grunt/connect.js and swagger-editor now runs via my fully qualified host name. Thanks, @mohsen1 

On Thursday, January 8, 2015 at 4:16:25 PM UTC-5, David Biesack wrote:

done: https://github.com/swagger-api/swagger-editor/issues/294