search

usnistgov / SpectrumBrowser

ITL
12 stars 11 forks source link

I changed the protocol to https and now I cannot load the spectragram #147

Closed jkubNTIA closed 9 years ago

jkubNTIA commented 9 years ago

I changed the protocol to https and then I restarted my website and I restarted nginx. When I try to generate the spectragram I get an error communicating with the server and this is in my server logs:

Log Message : URL = https://localhost:8443/spectrumbrowser/generateSingleAcquisitionSpectrogramAndOccupancy/ECR16W4XS/1405050141/LTE/703967500/714047500/user-142738217826958637726 sessionId: user-142738217826958637726 privilege: user updated session ID expireTime {'SensorID': u'ECR16W4XS', 'freqRange': u'LTE:703967500:714047500', 't': 1405050141} Read 560000 LeftColumns to exclude 0 right columns to exclude 0 Generated fig Log Message : Unpacking json object took 96 Log Message : Setting URL https://localhost:8000/generated/user-142738217826958637726/ECR16W4XS.1405050141.0.0.0.0.-75.0.png

: Invalid HTTP method: '\x16\x03\x01\x00\xbc\x01\x00\x00\xb8\x03\x03%\xd7X#3>\x82\x14\xba\xaa8\xec\xb7\x10\xdd\x0eHG\x17\xdf\x16<\xe62\x96@\x14}.@GP\x00\x00\x18\xc0+\xc0/\xc0\n' Log Message : bar value changed new value is 83 Log Message : Error loading image event: ErrorEvent:
jkubNTIA commented 9 years ago

I get the same error for both LTE & radar data.

jkubNTIA commented 9 years ago

I tried logging in to http://localhost:8000 (with my protocol still set to https) and I get the same type of error:

Log Message : URL = http://localhost:8000/spectrumbrowser/generateSingleAcquisitionSpectrogramAndOccupancy/ECR16W4XS/1405048340/LTE/703967500/714047500/user-142738237093735780002 sessionId: user-142738237093735780002 privilege: user updated session ID expireTime {'SensorID': u'ECR16W4XS', 'freqRange': u'LTE:703967500:714047500', 't': 1405048340} Read 560000 LeftColumns to exclude 0 right columns to exclude 0 Generated fig Log Message : Unpacking json object took 48 Log Message : Setting URL https://localhost:8000/generated/user-142738237093735780002/ECR16W4XS.1405048340.0.0.0.0.-75.0.png

: Invalid HTTP method: '\x16\x03\x01\x00\xbc\x01\x00\x00\xb8\x03\x03\xa2E\x02\n' Log Message : bar value changed new value is 83 Log Message : Error loading image event: ErrorEvent:
ranganathanm commented 9 years ago

If you set your protocol to https: then presumably port 8000 will be blocked for access by the firewall. Logging in using an http url is not allowed. So you should

  1. Specify https as the protocol.
  2. Only access the system via the public port (8443).

Ranga.

From: jkub01 notifications@github.com Sent: Thursday, March 26, 2015 11:08 AM To: usnistgov/SpectrumBrowser Subject: Re: [SpectrumBrowser] I changed the protocol to https and now I cannot load the spectragram (#147)

I tried logging in to http://localhost:8000 (with my protocol still set to https) and I get the same type of error:

Log Message : URL = http://localhost:8000/spectrumbrowser/generateSingleAcquisitionSpectrogramAndOccupancy/ECR16W4XS/1405048340/LTE/703967500/714047500/user-142738237093735780002 sessionId: user-142738237093735780002 privilege: user updated session ID expireTime {'SensorID': u'ECR16W4XS', 'freqRange': u'LTE:703967500:714047500', 't': 1405048340} Read 560000 LeftColumns to exclude 0 right columns to exclude 0 Generated fig Log Message : Unpacking json object took 48 Log Message : Setting URL https://localhost:8000/generated/user-142738237093735780002/ECR16W4XS.1405048340.0.0.0.0.-75.0.png : Invalid HTTP method: '\x16\x03\x01\x00\xbc\x01\x00\x00\xb8\x03\x03\xa2E\x02\n' Log Message : bar value changed new value is 83 Log Message : Error loading image event: ErrorEvent:

Reply to this email directly or view it on GitHubhttps://github.com/usnistgov/SpectrumBrowser/issues/147#issuecomment-86560403.

ranganathanm commented 9 years ago

It appears you did not change the port to 8443 on your configuration. I think your system is mis-configured.

8443 is the public facing port. Testing on port 8000 using http is not valid. Please check your configuration.

Ranga

jkubNTIA commented 9 years ago

Ah. I did not remember that we had a port in the Configuration file in addition to the protocol. Thanks. It works now.