Jump to content

ElectricBadger

Members
  • Content Count

    59
  • Joined

  • Last visited

Community Reputation

5 Neutral

About ElectricBadger

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I like the new dashboard, but is it possible for users to reorder the boxes? I'd like to have Parity appear above Shares and Users, as the utilization counters are useful to have on the screen without scrolling (even with Shares and Users collapsed, it doesn't quite fit on a 27" display — Edit: this is with the window sized for two columns. Making the window a bit wider gives a better layout, but it takes up rather a lot of the screen!) Similarly, I'd want to put Motherboard below Processor and Memory in the server view on the left, since it doesn't tend to change much, and you know when you've changed it Not suggesting making these changes for everybody, as everybody has different needs — but I can't see any way of reordering them myself.
  2. I thought I'd tidy up a bit and move all the sample files from the proxy-confs folder to proxy-confs/_samples. But something noticed I'd done that and automatically recreated them again a few minutes later. Having them in the sample folder as the live files makes it difficult to find what I want (and makes tab-completion more of a pain). Is there a way I can disable this auto-recreate, or tell it that the samples live in a different folder?
  3. Some people have animated avatars, but I find they make the actual content of the page incredibly difficult to read — they're like particularly bad banner ads, but you can't scroll them away because they're right next to what you're trying to read. I have added a particularly bad example to an ad-blocker just to get it off my screen, but that is not a particularly scalable solution Would it be possible to have a per-user config setting which would render just the first frame of these avatars, so those of us who can't read content with them around can still use the forum without breaking things for people who like them? (I assume there are people who like having animations all over the place — I'd happily disable them completely — but see https://alistapart.com/article/accessibility-for-vestibular/ for an example of why they should be optional.) Thanks!
  4. I'm trying to disable some features in data/config.php, but the Docker image does not set the permissions correctly for unRAID use. When I try "chmod 666 config.php; ls -l config.php" I see that my permission change has been ignored. I had to ssh into the unRAID server to edit this file. Is it possible for the image to set the permissions correctly so the config can be edited from appdata without this step? Thanks
  5. FCP is reporting this error on my unRAID 6.6.6 box: The plugins page shows that I'm running version 2018.08.29a of the system stats plugin, which the release notes claim is compatible with 6.6.6 — 2019.01.12 is the first version to set a minimum unRAID version of 6.7.0. (The plugins page, quite correctly, won't let me update to this.) Is FCP scanning against the latest released version of the plugin rather than the currently installed one? That seems a bit odd to me — and it certainly shouldn't be reporting it as an error when the fix involves installing a release candidate version of unRAID, as that's not really an option for important systems…
  6. I set mine up from the Spaceinvaderone video — if you followed a different tutorial, your configs might well be a bit different.
  7. Are you using the subfolder config for Nextcloud rather than the subdomain — do you normally access it through "MyDomain".duckdns.org/nextcloud? What include do you have at the bottom of site-confs/default? I'm using subdomains throughout, so I have include /config/nginx/proxy-confs/*.subdomain.conf; If you're including *.subfolder.conf instead, it's probably worth adding this line above it — but I'm not sure if there are any issues mixing subfolder and subdomain setups.
  8. Looks like there's a problem with the SSL certificate, not the GitLab config. Have you added the "git" subdomain to the list of the subdomains in the letsencrypt docker?
  9. I've got this in my nginx config (in proxy-confs/gitlab-ce.subdomain.conf): server { listen *:80; server_name registry.subdomain.duckdns.org; server_tokens off; return 301 https://$http_host:$request_uri; access_log /config/log/nginx/gitlab_registry_access.log; error_log /config/log/nginx/gitlab_registry_error.log; } server { listen *:443 ssl; server_name registry.subdomain.duckdns.org; server_tokens off; include /config/nginx/ssl.conf; client_max_body_size 0; chunked_transfer_encoding on; access_log /config/log/nginx/gitlab_registry_access.log; error_log /config/log/nginx/gitlab_registry_error.log; location / { include /config/nginx/proxy.conf; proxy_pass http://gitlab:9381; } location /v2/ { include /config/nginx/proxy.conf; add_header 'Docker-Distribution-Api-Version' 'registry/2.0' always; proxy_pass http://gitlab:9381; } } and this as the container's extra parameters (minus setup for email, backups and container registry): --env GITLAB_OMNIBUS_CONFIG="external_url 'https://git.subdomain.duckdns.org';registry_external_url 'https://registry.subdomain.duckdns.org';gitlab_rails['gitlab_ssh_host']='git.subdomain.duckdns.org';nginx['listen_port']=9080;nginx['listen_https']=false;nginx['hsts_max_age']=0;registry_nginx['listen_port']=9381;registry_nginx['listen_https']=false;registry_nginx['enable']=true;registry['enable']=true;" If you want to use ssh rather than https for cloning/pushing, you'll need to add a port to the container for it: host port 9022 (or whatever you like that isn't being used), container port 22. I then add this in ~/.ssh/config: Host gitlab HostName git.subdomain.duckdns.org Port 9022 User gitlab although I have to say that, while this works for Mac and Linux/BSD, I have no idea what the equivalent is for Windows!
  10. I've found that the network type is the cause of the problem — when this is set, unRAID allows setting the host port but not the container port. To fix, change the network type to "bridge", add/edit the port setting, then change the network type back to "proxynet". I'm not sure if this is an unRAID bug or not — it doesn't seem like the correct behaviour, but I'm not sure how unRAID is supposed to know what to do with a network created with "docker network create"…
  11. I'm trying to configure the Docker container registry on GitLab-CE but I don't seem to be able to add a port for it to listen on. I've added this to my extra parameters: registry['registry_http_addr']='192.168.69.99:9081';registry_nginx['enable']=false;registry['enable']=true; and added a redirect for port 9081, but it does not show in the container list after clicking "apply" (see screenshots). The container's network type is set to "proxynet", as per SpaceInvaderOne's nginx proxy video, so I can access the container registry from outside my own network. What could be going wrong here? Port 9081 doesn't seem to be mapped to any other containers (and, even if it was, I'd expect unRAID to open a dialog telling me this, rather than silently failing : ) and other ports I've tried fail to show up in a similar way.
  12. Thanks — I'd already noticed that after I posted, though. I changed "GitLab-CE" to "gitlab" and edited the name of the Docker image to "gitlab", but it didn't fix it. Changing the 80 in nginx['listen_port'] = 80; to 9080, which is the port that GitLab's actually listening on, however, did. Can't believe I didn't spot that 🙄 Thanks for your help!
  13. I'm trying to write a config file to reverse proxy to GitLab-CE, but I can't get it to connect. I have the following config: server { listen 443 ssl; server_name git.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_gitlab GitLab-CE; proxy_pass http://$upstream_gitlab:9080; } } and this as extra parameters for the GitLab-CE docker, minus config for email and backups (and with the real domain replaced with example.com): --env GITLAB_OMNIBUS_CONFIG="external_url 'https://git.example.com';gitlab_rails['gitlab_ssh_host']='192.168.69.99';" but I just get 502 Bad Gateway when I try to connect. The page at https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/settings/nginx.md#supporting-proxied-ssl suggests adding nginx['listen_port'] = 80; nginx['listen_https'] = false; but this hasn't helped at all. The nginx error log has this: 2018/09/22 14:26:57 [error] 372#372: *224 connect() failed (111: Connection refused) while connecting to upstream, client: <MY EXTERNAL IP>, server: git.*, request: "GET / HTTP/1.1", upstream: "http://172.18.0.3:9080/", host: "git.example.com" TBH, I'm a bit stumped here. Does anybody have any clue as to what could be going wrong? Thanks 😎
  14. Hi I'm trying to find how to specify my Cloudflare DNS API key in the letsencrypt + nginx docker, so I went to the thread: and searched for cloudflare api. I got back search results claiming to be for "cloudflare" OR "api", with a link to click to search for "cloudflare AND api". I think that AND should be the default: Google, eBay and Amazon all default to AND, and these are probably the three most used search boxes on the Internet! It's not good to break user expectations just for the sake of it… (Yes, there's an option on the dropdown — but I don't see any way I can configure "AND" to be the default! Could we maybe have a user preference for this?) This is particularly annoying with the timeout between searches, as you have to wait for the timeout if you get it wrong. I could understand having that for anonymous users, but logged-in users should be able to search again straight away — anybody abusing the system could be warned and banned if they keep hammering the server. Finally, after all this, I still don't get results containing "api". A search for the term on its own produces "There were no results for your search. Try broadening your criteria or choosing a different content area." — this is despite my having seen posts on the thread that contain the term. Has "api" been configured as a stop word? If so, please could you change that? It's a pretty useful term to be able to search for in a lot of the Docker threads… I did find what I was looking for in the end (in the appdata's dns-conf folder) but I had to use DuckDuckGo to find the info…