Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Discuss
  3. [Intranet] Install cloudron in a corporate network environment

[Intranet] Install cloudron in a corporate network environment

Scheduled Pinned Locked Moved Discuss
41 Posts 3 Posters 4.9k Views 4 Watching
  • 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.
  • girishG Offline
    girishG Offline
    girish
    Staff
    wrote on last edited by
    #31

    @rmdes apparently, node.js does not respect those variables. See thread at https://groups.google.com/g/nodejs/c/2ZFLIAUfTFs?pli=1 . Maybe https://github.com/TooTallNate/proxy-agents/tree/main/packages/proxy-agent

    rmdesR 1 Reply Last reply
    0
    • rmdesR Offline
      rmdesR Offline
      rmdes
      wrote on last edited by
      #32

      I'm going to investigate redsocks

      in the meantime the only error remaining has to do with collectd, the service appears to be running fine
      but the graphie containers freaks out as if graphite had never been initialized

      ┐
      │                                                                                                                                                                   │
      │   WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0x55988453aa90 pid: 19 (default app)                                                               │
      │   *** uWSGI is running in multiple interpreter mode ***                                                                                                           │
      │   spawned uWSGI master process (pid: 19)                                                                                                                          │
      │   spawned uWSGI worker 1 (pid: 26, cores: 1)                                                                                                                      │
      │   spawned uWSGI worker 2 (pid: 27, cores: 1)                                                                                                                      │
      │   2024-04-02 09:38:27,960 INFO success: uwsgi entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)                                       │
      │   2024-04-02 09:38:27,960 INFO success: carbon-cache entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)                                │
      │   2024-04-02 09:38:27,963 INFO spawned: 'whisper-cleanup' with pid 28                                                                                             │
      │   Cleanup old whisper databases...                                                                                                                                │
      │   find: ‘/var/lib/graphite/whisper/collectd/localhost/’: No such file or directory                                                                                │
      │   2024-04-02 09:38:27,978 INFO exited: whisper-cleanup (exit status 1; not expected)                                                                              │
      │   2024-04-02 09:38:29,984 INFO spawned: 'whisper-cleanup' with pid 30                                                                                             │
      │   Cleanup old whisper databases...                                                                                                                                │
      │   find: ‘/var/lib/graphite/whisper/collectd/localhost/’: No such file or directory                                                                                │
      │   2024-04-02 09:38:30,000 INFO exited: whisper-cleanup (exit status 1; not expected)                                                                              │
      │   2024-04-02 09:38:33,007 INFO spawned: 'whisper-cleanup' with pid 32                                                                                             │
      │   Cleanup old whisper databases...                                                                                                                                │
      │   find: ‘/var/lib/graphite/whisper/collectd/localhost/’: No such file or directory                                                                                │
      │   2024-04-02 09:38:33,022 INFO exited: whisper-cleanup (exit status 1; not expected)                                                                              │
      │   2024-04-02 09:38:34,023 INFO gave up: whisper-cleanup entered FATAL state, too many start retries too quickly     
      
      1 Reply Last reply
      0
      • girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by
        #33

        @rmdes you docker stop graphite, rm -rf /home/yellowtent/platformdata/graphite/* and then docker start graphite.

        rmdesR 1 Reply Last reply
        0
        • girishG girish

          @rmdes you docker stop graphite, rm -rf /home/yellowtent/platformdata/graphite/* and then docker start graphite.

          rmdesR Offline
          rmdesR Offline
          rmdes
          wrote on last edited by
          #34

          @girish just did, but it stays in the same state :

          2f718864-44b3-4351-bb33-5e7da3eb82a5-image.png

          1 Reply Last reply
          0
          • rmdesR Offline
            rmdesR Offline
            rmdes
            wrote on last edited by rmdes
            #35

            Hmm redsocks is difficult, I need more time to analyze which local IP I have to configure so that requets are temporarily routed to it

            2024/04/02 14:44:39 [error] 88905#88905: *1350 upstream prematurely closed connection while reading response header from upstream, client: 10.200.3.157, server: my.c
            loudron.***.****.***, request: "POST /api/v1/appstore/register_cloudron_with_setup_token HTTP/2.0", upstream: "http://127.0.0.1:3000/api/v1/appstore/register_cloudro
            n_with_setup_token", host: "my.cloudron.***.****.***", referrer: "https://my.cloudron.***.****.***/"
            2024/04/02 14:44:39 [error] 88905#88905: *1350 connect() failed (111: Unknown error) while connecting to upstream, client: 10.200.3.157, server: my.cloudron..***.****.***, request: "GET /api/v1/cloudron/status HTTP/2.0", upstream: "http://127.0.0.1:3000/api/v1/cloudron/status", host: "my.cloudron.***.****.***", referrer: "https:/
            /my.cloudron.***.****.***/"
            
            

            i'm wondering if there is a curl command I could do to register this token and then a file I could edit with the token

            1 Reply Last reply
            0
            • nebulonN Offline
              nebulonN Offline
              nebulon
              Staff
              wrote on last edited by
              #36

              The cloudron will rely more on the api server for example to contact the app store, so the Cloudron will need to be able to reach that anyways.

              1 Reply Last reply
              1
              • girishG girish

                @rmdes apparently, node.js does not respect those variables. See thread at https://groups.google.com/g/nodejs/c/2ZFLIAUfTFs?pli=1 . Maybe https://github.com/TooTallNate/proxy-agents/tree/main/packages/proxy-agent

                rmdesR Offline
                rmdesR Offline
                rmdes
                wrote on last edited by
                #37

                @girish i'm able to get npm packages just fine by having my .npmrc configured to use my intranet proxy, I wonder if the systemd box service couldn't be used to also use npmrc ?

                1 Reply Last reply
                0
                • girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by
                  #38

                  @rmdes no, we have to write code to make box code work with a http proxy. node.js does not support it out of the box. npm has written special code to make this work.

                  1 Reply Last reply
                  1
                  • rmdesR Offline
                    rmdesR Offline
                    rmdes
                    wrote on last edited by
                    #39

                    huh okay, but does this mean I'm the only one having deployed (more or less) cloudron in this context ?

                    girishG 1 Reply Last reply
                    0
                    • rmdesR rmdes

                      huh okay, but does this mean I'm the only one having deployed (more or less) cloudron in this context ?

                      girishG Offline
                      girishG Offline
                      girish
                      Staff
                      wrote on last edited by girish
                      #40

                      @rmdes yes, we am not aware of anyone deploying cloudron with just a http(s) proxy. It's not tested or supported. there's probably more failures down the line. Basically, anything non-http won't work (dns,email etc)

                      1 Reply Last reply
                      0
                      • rmdesR Offline
                        rmdesR Offline
                        rmdes
                        wrote on last edited by
                        #41

                        Indeed I'm aware of this, my goal was more the access to app-store and smooth app upgrades and of course : Active Directory support to enable easy SSO in my context.

                        And because we have our self-signed certificate deployed across our entire Windows Desktop park, I was thinking that would have been enough to sign my "cloudron.intranet.domain" with our root certificate and then enable anyone in the IT dept to access a set of applications.

                        1 Reply Last reply
                        0
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        • Login

                        • Don't have an account? Register

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Bookmarks
                        • Search