ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Testing SnipeIT on Fedora

    Scheduled Pinned Locked Moved IT Discussion
    snipe-itfedora
    62 Posts 12 Posters 10.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • JaredBuschJ
      JaredBusch
      last edited by

      Here is my Nginx reverse proxy conf file.

      [jbusch@proxy ~]$ sudo cat /etc/nginx/conf.d/assets.domain.com.conf 
      [sudo] password for jbusch: 
      server {
          client_max_body_size 40M;
          listen 443;
          server_name assets.domain.com;
          ssl          on;
          ssl_certificate /etc/letsencrypt/live/assets.domain.com-0001/fullchain.pem;
          ssl_certificate_key /etc/letsencrypt/live/assets.domain.com-0001/privkey.pem;
          ssl_stapling on;
          ssl_stapling_verify on;
          ssl_protocols TLSv1.2 TLSv1.1 TLSv1;
          ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
          ssl_prefer_server_ciphers on;
          ssl_session_cache shared:SSL:10m;
      #    ssl_dhparam /etc/ssl/certs/dhparam.pem;
          add_header Strict-Transport-Security "max-age=31536000; includeSubdomains";
      
          location / {
              proxy_set_header X-Real-IP $remote_addr;
              proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
              proxy_set_header Host $http_host;
              proxy_set_header X-NginX-Proxy true;
              proxy_set_header X-Forwarded-Proto $scheme;
              proxy_pass https://10.202.0.43;
              proxy_redirect off;
      
              # Socket.IO Support
              proxy_http_version 1.1;
              proxy_set_header Upgrade $http_upgrade;
              proxy_set_header Connection "upgrade";
      
          }
      }
      
      server {
          client_max_body_size 40M;
          listen 80;
          server_name assets.domain.com;
          rewrite        ^ https://$server_name$request_uri? permanent;
      }
      [jbusch@proxy ~]$ 
      
      hobbit666H 1 Reply Last reply Reply Quote 0
      • hobbit666H
        hobbit666
        last edited by

        Something still not right but home time and day off tomorrow 😄
        So will pick up Monday.

        Quick question apart from changing the APP_URL and APP_TRUSTED_PROXIES, have you done anything else on the Snipe server to make it "work" under https? Like .htaccess or Virtual Host files?

        1 Reply Last reply Reply Quote 1
        • G
          gtech
          last edited by

          Hi Guys

          Great info. I Installed SnipeIT on Centos 7 min, get it up however I can't add new users. Please advise.

          Thanks

          black3dynamiteB ObsolesceO 2 Replies Last reply Reply Quote 0
          • black3dynamiteB
            black3dynamite @gtech
            last edited by black3dynamite

            @gtech said in Testing SnipeIT on Fedora:

            Hi Guys

            Great info. I Installed SnipeIT on Centos 7 min, get it up however I can't add new users. Please advise.

            Thanks
            Click on Create New and then user.
            0_1532028020424_ce0b3c5f-c9c1-4a9b-a700-998d42ae8a93-image.png

            1 Reply Last reply Reply Quote 0
            • ObsolesceO
              Obsolesce @gtech
              last edited by

              @gtech said in Testing SnipeIT on Fedora:

              Hi Guys

              Great info. I Installed SnipeIT on Centos 7 min, get it up however I can't add new users. Please advise.

              Thanks

              I sync'd it to AD.

              1 Reply Last reply Reply Quote 0
              • G
                gtech
                last edited by

                My bad, left out some details. when I full out the create user info form, submit it I get "Whoops, looks like something went wrong."

                ObsolesceO black3dynamiteB 2 Replies Last reply Reply Quote 0
                • ObsolesceO
                  Obsolesce @gtech
                  last edited by

                  @gtech said in Testing SnipeIT on Fedora:

                  My bad, left out some details. when I full out the create user info form, submit it I get "Whoops, looks like something went wrong."

                  That's not very informative. What's the log say?

                  1 Reply Last reply Reply Quote 0
                  • black3dynamiteB
                    black3dynamite @gtech
                    last edited by

                    @gtech said in Testing SnipeIT on Fedora:

                    My bad, left out some details. when I full out the create user info form, submit it I get "Whoops, looks like something went wrong."

                    Open .env and change APP_DEBUG=false to true. So you can see more information than "Whoops, looks like something went wrong."

                    1 Reply Last reply Reply Quote 2
                    • G
                      gtech
                      last edited by

                      SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'activated' cannot be null (SQL: insert into users....

                      DustinB3403D 1 Reply Last reply Reply Quote 0
                      • DustinB3403D
                        DustinB3403 @gtech
                        last edited by DustinB3403

                        @gtech said in Testing SnipeIT on Fedora:

                        SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'activated' cannot be null (SQL: insert into users....

                        Create an issue on snipe-it's GitHub. You can also pop in to their gutter.im/snipe-it and see if they can assist you

                        1 Reply Last reply Reply Quote 2
                        • hobbit666H
                          hobbit666 @JaredBusch
                          last edited by

                          @jaredbusch Thanks
                          Must of been a setting i was missing in my NGINX conf file. Made it too look more like yours and i'm working 🙂

                          1 Reply Last reply Reply Quote 2
                          • 1
                          • 2
                          • 3
                          • 4
                          • 4 / 4
                          • First post
                            Last post