Skip to content
This repository has been archived by the owner on Feb 18, 2021. It is now read-only.

When I login the saltpad ,I get Network Error #174

Open
Leno730 opened this issue Jun 22, 2016 · 4 comments
Open

When I login the saltpad ,I get Network Error #174

Leno730 opened this issue Jun 22, 2016 · 4 comments

Comments

@Leno730
Copy link

Leno730 commented Jun 22, 2016

When I login the saltpad ,I get Network Error
my salt-api version is:
salt-api 2016.3.1 (Boron)

rest_cherrypy config is :
rest_cherrypy:
port: 8000
host: 0.0.0.0
disable_ssl: True

thannks!

@azabielski
Copy link

I am getting the same thing with tornado with ssl

rest_tornado:
    # can be any port
    port: 8000
    ssl_crt: /etc/pki/tls/certs/mine.com.crt
    # no need to specify ssl_key if cert and key
    # are in one single file
    ssl_key: /etc/pki/tls/certs/minecom.key
    debug: False
    disable_ssl: False
    websockets: True
    cors_origin: '*'


{
  "API_URL": "s.mine.com:8000",
  "SECURE_HTTP": "true",
  "FLAVOUR": "rest_tornado"
}

<VirtualHost *:443>
  SSLEngine on
  SSLCertificateFile /etc/pki/tls/certs/mine.com.cer
  SSLCertificateKeyFile /etc/pki/tls/certs/mine.com.key
  SSLCertificateChainFile /etc/pki/tls/certs/comodo_intermediate.crt
  SSLCACertificateFile /etc/pki/tls/certs/comodo_root.crt

  Header always set Strict-Transport-Security "max-age=15768000"

  ServerName s.mine.com
  ServerAdmin [email protected]
  LogLevel warn
  ErrorLog "/var/log/apache2/saltpad-error.log"
  CustomLog "/var/log/apache2/saltpad-access.log" combined

  # Saltpad specific
  DocumentRoot /salt/saltpad
  <Directory "/salt/saltpad">
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} !index
    RewriteRule (.*) /index.html [L]
    #FallbackResource /index.html
    AllowOverride All
    Require all granted
    Allow from all
  </Directory>


  SSLProxyEngine on
  SSLProxyVerify none
  SSLProxyCheckPeerCN off
  SSLProxyCheckPeerName off
  SSLProxyCheckPeerExpire off
  <Location "/api/">
    ProxyPass "https://s.mine.com:8000"
  </Location>

  SSLProtocol             all -SSLv3 -TLSv1 -TLSv1.1
  SSLCipherSuite          ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-
AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256
  SSLHonorCipherOrder     on
  SSLCompression          off
  SSLSessionTickets       off

</VirtualHost>

@lancepowell
Copy link

lancepowell commented Jul 14, 2016

see the same thing with both cherry and tornado, with ssl disabled.

When i do debug on the salt-api, i don't ever see the request come through. In chrome I see the request going to the right place but the api isn't logging anything about rejecting it. It's something with our saltpad config or with our apache or ngnix config.

@jaymecox-pinterest
Copy link

I'm also seeing this same problem. I get the login page, but clicking login shows the 'Network Error' even though it's not making any requests to nginx or salt-api backend.

@absmith82
Copy link

I'm not getting the network error at this point, however it doesn't seem to be submitting the login form. I see the salt-api registering the initial access to the page, but when the login form button is pushed I don't see it hitting the salt-api

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants