primordic/IssueDupesLite huggingface dataset:
Repository: nextcloud/nextcloudpi

Issue #1624: default for php max children is too low
Created: 2022-10-09T15:27:43Z
Compare #1439
Currently, the default for the php.ini setting pm.max_children is 6, which can easily be exhausted (e.g. by one or two NC desktop clients), causing further requests to timeout.
We should increase this value e.g. to always be >= 16 and <= SYSTEM_MEMORY / 100MB

Duplicate issue #1665: NextCloud GUI blocked when I download a file with IDM (Internet Download Manager)
Created: 2022-11-24T11:46:25Z
Hi I’m using NextCloud (NextCloudPi 1.50.2 - NC 24.0.5) installed on Rasperry Pi4 with Docker and Portainer.
When I try to download a file with IDM (Internet Download Manager) as soon as the download starts, the NextCloud GUI remains blocked for all users for a long time. If I download the files without IDM everything works perfectly. Is it possible that the block is caused by the overload of the multiple connections that IDM creates to download the file? … is there a way to set the NextCloud server to prevent or limit multiple connections on the same file?
I tried to change several php-fpm configuration parameters:
pm = static
pm.max_children = 100
pm.start_servers = 12
pm.min_spare_servers = 6
pm.max_spare_servers = 18
but the problem has not been solved.
At this point I think it's a NextCloudPi bug or a wrong configuration of the NextCloud server that I can't understand.
I must clarify that I am not an advanced user of Linux!
Thanks for your help.

Closing comment (2023-02-07T11:43:12Z): Possibly related to #1624
To be honest, though, this is more of a support request for a very specific hardware/software configuration that we frankly don't have the capacity to invest into.
If you find a solution that is related to a change in NCP, I'd love to know about it in order to incorporate it, but I can't provide any in-depth testing/troubleshooting myself.
Repository: nextcloud/nextcloudpi

Issue #1730: Debian 12 Bookworm Support
Created: 2023-02-11T18:38:21Z
For internal testing and notes. Do not expect support!!!!!! Please do report testing issues here.

#1887

Debian 12 Bookworm - release schedule
June 10th release date from https://wiki.debian.org/DebianBookworm
Assume mid-2023 for formal stable.

Duplicate issue #1856: Add booksworm support for install.sh script
Created: 2023-12-20T21:50:00Z
Description
Currently, in etc/ncp.cfg the config entry of the release is "release": "bullseye" but in the meantime, booksworm (one version above bullseye was released stable) and the install.sh returns an error

Closing comment (2023-12-27T16:25:05Z): Duplicate of #1730
bookworm is not yet supported and will not be until a bit of groundwork has been done (do not expect bookworm support before 2024-03).
Repository: nextcloud/nextcloudpi

Issue #1475: NC-Info: ports closed
Created: 2022-05-11T12:59:41Z
NCP v1.47.2
Debian 11 x86_64 curl installation
The ports are shown closed but are open and everything is working has expected.
The problem happens after a new installation (clean Debian install)
NextCloudPi version  v1.47.2
NextCloudPi image    NextCloudPi_05-11-22
OS                   Debian GNU/Linux 11. 5.10.0-14-amd64 (x86_64)
automount            yes
USB devices          sdb
datadir              /data/ncdata/data
data in SD           no
data filesystem      btrfs
data disk usage      105G/207G
rootfs usage         5,7G/16G
swapfile             /var/swap
dbdir                /data/ncdatabase
Nextcloud check      ok
Nextcloud version    23.0.4.1
HTTPD service        up
PHP service          up
MariaDB service      up
Redis service        up
HPB service          up
Postfix service      up
internet check       ok
port check 80        closed
port check 443       closed
IP                   REMOVED SENSITIVE VALUE
gateway              REMOVED SENSITIVE VALUE
interface            enp1s0
certificates         REMOVED SENSITIVE VALUE
NAT loopback         yes
uptime               9:02

Duplicate issue #1486: Open ports check fail due to a bug in ncp-diag file
Created: 2022-06-05T14:53:55Z
ncp-diag file
Line 79
Add "/check" after "https://portchecker.co"
Otherwise port check 80 and 443 anwser "closed" erroneously (even when these ports are correctly opened and working)
Congratulations for you exelent work and thanks to you and all ncp comunity.

Closing comment (2022-07-27T09:17:43Z): Can confirm the bugfix too. @Soiuke Do you mind to create a fork plus a corresponding pull-request?
BTW: This issue is the same as #1475 , isn't it?

@schoetju I've not created a fork and pull-request because I think that this is a "minor" issue, which does not affect the main functionality of the project. As far as @theCalcaholic knows about the issue and also the proposed solution, I think that he can modify ncp-diag file in the main project/branch.
Otherwise please tell me if I must open a fork and pull-request in order to incorporate the solution to the main project.
By the other hand, I apologize for duplicating issues.
Thanks to all the ncp community. Congratulations to @nachoparker for his great work during last years, and thanks to @theCalcaholic for leading the project from now on.
Repository: nextcloud/nextcloudpi

Issue #1697: OCC Segmentation fault after upgrading to v1.50.5
Created: 2023-01-11T16:27:35Z
After upgrading from last version to v1.50.5 the automatic file scan does not work any more. In the logs i found a Segmentation fault error.
Running nc-scan /usr/local/bin/ncc: line 3: 2505817 Segmentation fault      ${SUDO} php /var/www/nextcloud/occ "$@" /usr/local/bin/ncc: line 3: 2505820 Segmentation fault      ${SUDO} php /var/www/nextcloud/occ "$@" Done. Press any key...

Duplicate issue #1672: coredump /usr/sbin/php-fpm8.1
Created: 2022-12-03T16:58:38Z
I started using nextcloudpi via docker-compose on an up-to-date endeavouros.  I see several coredumps for /usr/sbin/php-fpm8.1.
Just one example out of 156 coredumps from the last 4 days:
# coredumpctl info 16775
           PID: 16775 (php-fpm8.1)
           UID: 33 (http)
           GID: 33 (http)
        Signal: 11 (SEGV)
     Timestamp: Sat 2022-12-03 17:33:50 CET (20min ago)
  Command Line: $'php-fpm: pool www'
    Executable: /usr/sbin/php-fpm8.1
 Control Group: /system.slice/docker-60963f79d0e89de4a1754d3cd572d5b1c022b6eaca00f64f844daaf11a54fea7.scope
          Unit: docker-60963f79d0e89de4a1754d3cd572d5b1c022b6eaca00f64f844daaf11a54fea7.scope
         Slice: system.slice
       Boot ID: b96d7fb0b0d84463aa28875582a04c3c
    Machine ID: 4bd88beaa35549b5922de02c8064cbf1
      Hostname: 60963f79d0e8
       Storage: /var/lib/systemd/coredump/core.php-fpm8\x2e1.33.b96d7fb0b0d84463aa28875582a04c3c.16775.1670085230000000.zst (inaccessible)
       Message: Process 16775 (php-fpm8.1) of user 33 dumped core.
                
                Stack trace of thread 113:
                #0  0x00007f776d51425c n/a (/usr/lib/php/20210902/opcache.so + 0x1c25c)
                ELF object binary architecture: AMD x86-64

Versions:
docker 1:20.10.21-1
ownyourbits/nextcloudpi-x86   latest 
NextCloudPi 24.0.5

docker -compose.yml
# cat docker-compose.yml     
version: '3'
services:
  nextcloudpi:
    image: ownyourbits/nextcloudpi-x86
    command: "${IP}"
    restart: always
    ports:
     - "8080:80"
     - "443:443"
     - "4443:4443"
    volumes:
     - /mnt/zstore/nextcloudpi/data:/data
     - /etc/localtime:/etc/localtime:ro
    # for nc-encrypt
    devices:
      - /dev/fuse:/dev/fuse
    # for nc-encrypt # NOTE: take a look at this https://github.com/docker/for-linux/issues/321#issuecomment-677744121
    cap_add:
      - SYS_ADMIN
    container_name: nextcloudpi

volumes:
  ncdata:

Closing comment (2023-01-21T18:25:54Z): Probable duplicate of #1697
Repository: nextcloud/nextcloudpi

Issue #92: nc-update updates nextcloud to v12.0.1? 
Created: 2017-08-08T09:22:50Z
Does it?
I tried to update nextcloud but it gives error in first step about expected files
.Well-known

Duplicate issue #91: Updating n-update will update nextcloud to v12.0.1
Created: 2017-08-08T09:17:21Z
What version of NextCloudPi are you using? ( eg: v0.17.2 )
What is the base image that you installed on the SD card? ( eg: NextCloudPi_07-21-17 )
Expected behavior
Actual behaviour
Steps to reproduce, from a freshly installed image
Include logs

Nextcloud logs
Login as admin user into your Nextcloud and copy here the logs from
https://example.com/index.php/settings/admin/logging

If you don't have access to the web interface, open a terminal session and paste the last 100 lines of /var/www/nextcloud/data/nextcloud.log



Apache logs
Paste the output of `systemctl status apache2`
Paste the output of `tail -n 100 /var/log/apache2/*.log`



mariaDB logs
Paste the output of `systemctl status mysqld`
Paste the output of `tail -n 100 /var/log/mysql/*.log`

Closing comment (2017-08-08T09:54:06Z): Duplicate of #92
Repository: nextcloud/nextcloudpi

Issue #37: automount and moving swapfile bug
Created: 2017-07-05T17:50:11Z
Not so much an issue as some questions.  I used the NCPi-config to move my swap file to my external hard disk.  That works fine.  Now, when I use the "free -t" command, it lists swap 0 Total, 0 used, and 0 free.  I think that Raspbian is NOT recognizing the move of the swap file.  I do see that the dphys-swapfle config file for swap does point the the correct location and is the correct size.
Just wondering if you are seeing the same thing. I am asking because I installed RPi-Monitor and it displays the swap file info.  It get's that data from /proc/meminfo.  on my machine that  shows 0 for both total and available swap.  I would like to get RPi-Montior working with the correct  swap info if possible.

Duplicate issue #56: No space left, swapfile is generated in SD card
Created: 2017-07-17T21:16:19Z
Hi,
I changed the filesystem of my external from NTFS to ext4, which caused a bootloop on my Raspi because I didn't remove the respective line from fstab first. Good thing it booted into recovery mode so I did that. While I was at it, I changed the swapfile configuration, as it was located on the external. In order to do that, I just removed both the location and the filesize... Now I can boot into the system but when I'm in nextcloudpi-config, I get the error that there's no space left on the device, so I can't relocate the database to my external in order to pick up where I left off. If I plug-in the SD card into my Windows computer, it shows me that there's 19,4 MB of 40,3 MB left... What should I do?
Thanks!

Closing comment (2017-07-18T08:00:55Z): Duplicate of #37
Repository: nextcloud/nextcloudpi

Issue #293: Letsencrypt without Port 80 Setup
Created: 2017-11-14T07:45:47Z
I have found a script that possibly can be ported to nextcloudpi for using letsencrypt and duckdns when port 80 is blocked by ISP. I am no coder, but I have looked through it and it looks plausible.
The script is found at https://github.com/lukas2511/dehydrated/blob/master/dehydrated
The author has a tutorial for the project/script found here.
Is there any way this is possible to integrate into the ncp config?

Duplicate issue #636: Issue with letsencrypt.sh and IPv6 address
Created: 2018-09-16T19:06:21Z
When using an IPv6 only DDNS configuration, letsencrypt.sh shows the following output:
[ letsencrypt ]
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for [subdomain].spdns.org
Using the webroot path /var/www/nextcloud for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. [subdomain].spdns.org (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://[subdomain].spdns.org/.well-known/acme-challenge/WFxbUkPyYZnWfJnj-iJDdRuKAoF8Z9ZohepTHbeLYmI: Error getting validation data
IMPORTANT NOTES:
- The following errors were reported by the server:

Domain: [subdomain].spdns.org
Type: connection
Detail: Fetching
http://[subdomain].spdns.org/.well-known/acme-challenge/WFxbUkPyYZnWfJnj-iJDdRuKAoF8Z9ZohepTHbeLYmI:
Error getting validation data

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

Using an IPv4 address with the same settings works well.

Closing comment (2018-09-16T21:30:54Z): Related to #293.
Repository: nextdns/nextdns

Issue #305: Respect forwarder order
Created: 2020-08-23T20:08:25Z
In the config file I set:
forwarder https://dns.google/dns-query#8.8.8.8,https://dns.nextdns.io#45.90.28.0
But all queries seem to go to NextDNS. I'd like the order to be respected so that Google is the main upstream server and only go to NextDNS if Google doesn't respond.

Duplicate issue #308: forwarder failover
Created: 2020-09-07T19:11:22Z
Hi,
Not a request really but more of a question. If I specify two forwarders does the CLI round-robin between them or try the second one if the first is not reachable? I started using this CLI today and noticed that even though I have two forwarders specified if the first one is down the CLI doesn't seem to try the second one.
Maybe it's just coincidence and it does round robin and I was unfortunate to hit the forwarder that was down each time ...
Thanks.

Closing comment (2020-09-08T17:34:32Z): Similar to #305

It's the opposite for me actually. :) The first entry was what went down each time and NextDNS couldn't resolve my home network as it couldn't contact that forwarder. If it did Round Robin like you suggested or there was an option to try the alternate forwarders if the first one is down that'd be great.
Repository: nextdns/nextdns

Issue #913: NextDNS package not reinstalled on UDM/UXP firmware upgrade
Created: 2024-02-21T17:24:29Z
nextdns is uninstalled from my unifi os (Dream Machine Pro) on every update.  I have boot scripts that run on each boot to re-configure things after this happens.  I'd like to add to those scripts the install command `sh -c 'sh -c "$(curl -sL https://nextdns.io/install)"'.  But this script requires user interaction.  I'd like a way to run it in silent mode without the need for user interaction.  I have subsequent commands to configure nextdns in my boot script.

Duplicate issue #947: NextDNS installation on Unifi Cloud Gateway Ultra is not persistent
Created: 2024-05-24T19:59:32Z
Context

CLI Version: nextdns version 1.43.3
Platform: Unifi Cloud Gateway Ultra

Although NextDNS installs and works fine on Unifi Cloud Gateway Ultra it breaks after a firmware update because not all of the components are installed in a persistent location.
Happened both on upgrade from 3.2.12 to 3.2.17 and from 3.2.17 to 4.0.4
detect_os  debian
detect_goarch: arm64
detect_goos: linux
bin_location: ERROR: Unknown bin location for

Closing comment (2024-05-24T20:02:35Z): Dup of #913
Repository: nextdns/nextdns

Issue #457: Installation of CLI on UDM does not allow queries from Guest network
Created: 2021-04-16T16:47:16Z
<Describe the bug>
After installing the NextDNS CLI on my UDM by following the instructions here on Github, no DNS server can be reached from the Guest network when DHCP points DNS at the router itself (set to auto).
After troubleshooting this issue, it appears this is because the Guest network on UDM by default only allows traffic directed to the router over ICMP, standard DNS ports, and DHCP ports.
I was able to resolve this by adding a FW rule under GUEST LOCAL allowing traffic to the router over port 5553 TCP and UDP. Now queries reach the CLI and are resolved successfully.
This may be a known issue and unable to be resolved with the installation script, but if so, maybe it should be noted in the UDM instructions?

Context

Version [e.g. 1.5.2]: 1.11.0
Platform [e.g. macOS, ASUS-Merlin]: UDM

Duplicate issue #562: Unifi Dream Machine Pro Isolated Networks lose resolution  
Created: 2021-08-15T15:59:09Z
I have a Unifi Dream Machine Pro which I’ve installed the CLI on to. For my IoT network, which I run with Device Isolation enabled, nothing on that network will resolve DNS until I disable Device Isolation.
I’ve tried adding local and remote dns IPs to the allow list but it does not help fix it.

Closing comment (2022-06-30T16:17:55Z): This is a duplicate of #457.

Edit on UDM isolated network != guest

I think the fix is largely going to be the same? I was only trying to stitch the issues together.

it's possible but i doubt, since guest is by default (and not possible to disable) isolated, where isolated network must be manually defined, so even if the problem is the same i think the fix (in cli way) must be different (but i can be wrong).

Network isolation is enforced by the Guest Hotspot profile, which you can in fact edit. If you wanted, you could allow a guest network to fully communicate with non-guest networks (more commonly you may allow communication to a jump box, specific hosts, or specific ports like ssh).

Anyways, I can report that the instructions worked with Network 7.2.87 for my guest network.
Repository: nextdns/nextdns

Issue #341: Better interop with dnsmasq on a router with multiple VLANs and local domains
Created: 2020-10-11T15:19:40Z
On an ER-X router, I use dnsmasq for both DHCP and DNS. I also use static DHCP for most hosts on the LAN to set custom names. The LAN is actually 3 VLANs, each VLAN has its own local domain name (e.g. .domain1, .guest, .iot) and the same dnsmasq instance serves clients on all 3 VLANs returning correct (static DHCP) IP addresses and the correct domain for each VLAN.
This all works fine with dnsmasq, clients on any VLAN can resolve other hosts on the VLANs either by shortname or shortname.domain.
I was hoping to use nextdns as replacement for dnsmasq but still keep dnsmasq for DHCP so that I can get client reporting in the nextdns logs.
The default install disables the DNS part in dnsmasq by setting port=0. When that happens, the host names in the DHCP leases file /run/dnsmasq-dhcp.leases no longer have the custom static DHCP names that I want, but instead they have whatever the client reports or whatever dnsmasq may synthesize from MAC addresses, etc. This seems to be a limitation of dnsmasq if the DNS part doesn't run. Now nextdns cannot resolve hosts on my LAN by their custom names from static DHCP.
I figured that I'd just let dnsmasq run on some other port, say 5342 Now the short custom names show up in the leases file and nextdns can resolve them, but the FQDN names shortname.domain cannot be resolved because nextdns doesn't know about the VLAN domains.
I'm not sure what the correct way to set this up is, maybe dnsmasq needs to always run and use the nextdns setting forwarder for each VLAN domain. But it would be nice if the setup-router feature just worked out of the box without changing previous behavior that dnsmasq users are relying on.

Duplicate issue #343: discovery-dns only setting
Created: 2020-10-12T14:01:01Z
When discovery-dns is set to a dnsmasq server that also handles DHCP, looks at the hosts file on a router, etc. that should be a sufficient setting if dnsmasq is configured correctly. Is it possible to add finer control to disable looking at the dhcp leases file and mDNS just like we can set use-hosts false?
The problem is that nextdns will start responding for non-FQDN names and if the same names exist across different VLANs (with different domains), it seems to randomly return the wrong IP, some clients seem to try the short name first and then the FQDN name with the domain the client knows about (and which is correct for the VLAN of the client) if the short name does not resolve. At least I think this is what's happening, I can resolve a short name and get a different IP (though still correct in a different VLAN) than when I resolve the same FQDN name.
Or an option like the dnsmasq domain-needed to force use of FQDN only. Also see the related dhcp-fqdn setting in dnsmasq.

Closing comment (2020-10-12T14:09:38Z): Related to #341
Repository: nextdns/nextdns

Issue #309: nextdns log: Error: exec: "podman": executable file not found in $PATH
Created: 2020-09-08T04:29:41Z
Running nextdns log on Ubuntu 18.04.5 LTS results in
Error: exec: "podman": executable file not found in $PATH
Context

Version [e.g. 1.5.2]: 1.8.0
Platform [e.g. macOS, ASUS-Merlin]: Ubuntu 18.04.5 LTS

Duplicate issue #310: NextDNS 1.8.0 error
Created: 2020-09-08T07:59:58Z
The nextdns log gives the following error after upgrading to version 1.8.0 on armv7 (Raspberry Pi 4B running Raspbian):
$ sudo nextdns log
Error: exec: "podman": executable file not found in $PATH

It seems to be working fine apart from this.
I have another Pi running the same OS etc. and it is currently on NextDNS 1.7.1 and the log command works fine there.
Context

Version: 1.8.0
Platform: Linux 5.4.51-v7l+ #1333 SMP Mon Aug 10 16:51:40 BST 2020 armv7l GNU/Linux

Closing comment (2020-09-08T08:51:19Z): Dup #309
Repository: ng-packagr/ng-packagr

Issue #1431: Rollup 1.26 breaks fesm5 build of libraries
Created: 2019-10-28T10:57:07Z
Type of Issue
[x ] Bug Report
[ ] Feature Request

Description
ng-packagr declares a dependency on rollup that includes version 1.26.0. With this version we see that the fesm5 build of our library contains * exports.
I think that this is related to rollup/rollup#3196
This basically breaks the build of all of our libraries.
I suggest to set the dependency of ng-packagr to rollup@~1.25 until rollup fixes the bug.

Duplicate issue #1433: ERROR: Could not resolve <src_file> upgrading to version 5.5.0
Created: 2019-10-28T21:01:47Z
Type of Issue
[x ] Bug Report
[ ] Feature Request

Description & How To Reproduce
I tried upgrading ng-packgr to the latest version from 5.4.3 and got the following error.
Building Angular Package

------------------------------------------------------------------------------
Building entry point 'core'
------------------------------------------------------------------------------
Compiling TypeScript sources through ngc
Bundling to FESM2015
Bundling to FESM5
Bundling to UMD
ERROR: Could not resolve './src/module' from dist/core/fesm5/core.js
An unhandled exception occurred: Could not resolve './src/module' from dist/core/fesm5/core.js
See "/tmp/ng-UIo5O5/angular-errors.log" for further details.

I was able to create a completely stripped down version of my multiple library project and recreate the problem. Any ng-packagr version greater than or equal to 5.5.0 results in the error, but 5.4.3 does not. Wonder if you could take a quick look at the repo.
To recreate the issue clone this repo and run ...
npm i
npm run build

Please note the npm run build command in the package.json file. you can also change the version of ng-packagr to 5.4.3 and rerun the above to verify that it works.
Version Information
$ node_modules/.bin/ng-packagr --version
ng-packagr: >=5.5.0
@angular/*: 8.2.12
typescript: 3.5.3
rxjs: 6.5.3
node: 12.7.0
npm: 6.12.0

Closing comment (2019-10-28T22:08:30Z): Duplicate of #1431
Repository: ng-packagr/ng-packagr

Issue #728: How to disable the creating package of *.tgz
Created: 2018-03-27T12:03:17Z
Type of Issue
[ ] Bug Report
[ ] Feature Request
[x] Question

Description
This is a question (not a bug or feature)!
It is possible to disable the creating package of *.tgz?
I have nothing found about that in https://github.com/dherges/ng-packagr/blob/master/src/ng-package.schema.json
Version Information
$ node_modules/.bin/ng-packagr --version
ng-packagr: 2.4.1
@angular/compiler: 5.2.9
@angular/compiler-cli: 5.2.9
rollup: 0.55.5
tsickle: 0.27.2
typescript: 2.5.3

Duplicate issue #737: How to disable auto generate dist.tgz file?
Created: 2018-03-29T17:41:49Z
Type of Issue
[ ] Bug Report
[X] Feature Request

Description
I build my project to dist folder, after build I found there is a file named "dist.tgz" is generated, is there an option to disable it?
Version Information
$ node_modules/.bin/ng-packagr --version
"@angular/animations": "^5.2.9",
    "@angular/common": "^5.2.9",
    "@angular/compiler": "^5.2.9",
    "@angular/core": "^5.2.9",
    "@angular/forms": "^5.2.9",
    "@angular/http": "^5.2.9",
    "@angular/platform-browser": "^5.2.9",
    "@angular/platform-browser-dynamic": "^5.2.9",
    "@angular/router": "^5.2.9",
    "core-js": "^2.5.4",
    "rxjs": "^5.5.8",
    "zone.js": "^0.8.20",
    "@angular/cli": "1.7.3",
    "@angular/compiler-cli": "^5.2.9",
    "@types/jasmine": "2.8.6",
    "@types/node": "~9.6.1",
    "@types/gulp": "^4.0.5",
    "ng-packagr": "2.4.1",
    "gulp": "3.9.1",
    "gulp-rimraf": "0.2.2",
    "gulp-bump": "^3.1.0",
    "run-sequence": "^2.2.1",
    "rimraf": "^2.6.2",
    "shelljs": "0.8.1",
    "chalk": "2.3.2",
    "codelyzer": "~4.2.1",
    "jasmine-core": "~2.7.0",
    "jasmine-spec-reporter": "~4.1.1",
    "karma": "~1.7.0",
    "karma-chrome-launcher": "~2.2.0",
    "karma-cli": "~1.0.1",
    "karma-jasmine": "~1.1.0",
    "karma-jasmine-html-reporter": "^0.2.2",
    "karma-coverage-istanbul-reporter": "^1.3.0",
    "protractor": "~5.3.0",
    "ts-node": "~5.0.1",
    "tslint": "~5.9.1",
    "typescript": "~2.8.1"

Closing comment (2020-11-12T10:37:33Z): Duplicate of #728
Repository: ng-packagr/ng-packagr

Issue #1405: incorrect paths for import statement is generated
Created: 2019-09-21T18:05:18Z
Type of Issue
[x] Bug Report
[ ] Feature Request

Description
incorrect paths for import statement can be generated when a project has multiple library workspaces.
I think the following issue is similar to this issue.
#1109
How To Reproduce
I created a repository for reproduce this bug.

git clone  https://github.com/musou1500/test-angular-workspace
ng build lib2 && ng build lib1
open dist/lib1/lib/lib1.service.d.ts. then you can see an incorrect path for import on Lib1Service.test method.

    // should be ../../../dist/lib2/lib2
    test(): import("../../../../dist/lib2/lib2").Entity;
Expected Behaviour
the correct path for import statements should be generated.
Version Information
$ node_modules/.bin/ng-packagr --version
ng-packagr:            5.5.1
@angular/compiler:     8.2.7
rollup:                1.21.4
tsickle:               0.36.0
typescript:            3.5.3

Duplicate issue #2403: Implicitly inferred type from another entry point generates wrong import pathes in compiled library
Created: 2022-08-16T17:50:55Z
Type of Issue
[x] Bug Report
[ ] Feature Request

Description
Setup:

Library with at least two entry points, call them "entry2" and "entry3"
entry3 exports an interface
entry2 uses that interface (imports explicitly) in any file
Another file in entry2 references a value typed from the interface in entry3. Thanks to TypeScript type infering, the interface does not need to be imported in that file, as TypeScript can automatically infer the type from the assignment.
However what looks right and compiles fine leads to incorrect pathes in the compiled library: The d.ts file of the file containing the implicit reference to the interface looks something like this: "dist/entry2/interface"
This is a problem when publishing the library, because you won't have the library in that path when you installed it. This will lead to build errors in the consuming application

This appears to be a new problem in Angular 14 / ng-packagr 14
We used to have a setup like this for months now, and recently tried to upgrade to ng 14, which we can't until that bug is fixed or a workaround is found
How To Reproduce
See this demo repository, that contains a minimal reproduction example for the issue. You can find a setup similar to the one described above, only entry points "entry2" and "entry3" are relevant, just ignore the app and the main entry point of the lib
Expected Behaviour
The compiled library should always import from the public import path, like it used to did prior to ng 14
Version Information
ng-packagr:            14.1.0
@angular/compiler:     14.1.2
rollup:                2.78.0
typescript:            4.7.4
node: v16.16.0
npm: 8.11.0

Closing comment (2022-08-22T08:14:49Z): This is very similar to #1405
Repository: ng-packagr/ng-packagr

Issue #123: Inclusion of assets, or hooks during build for inclusion
Created: 2017-09-14T23:02:59Z
Type of Issue

 Bug Report
 Feature Request

Description
I currently have a convoluted build process for one of my component libraries. I've been able to almost completely replace with ng-packagr, but I have places where I manually create some core assets like images for these components as well as some scss.
I don't know if/how this fits into the ng-packagr story. I'd like the assets folder to be included in the build, but don't know if a current method exists for inclusion.

Duplicate issue #445: Include .js libraries and image assets
Created: 2017-12-26T07:11:00Z
Sorry if this has already been answered but I have been searching for a way to include images and script files from my assets folder. I would think this would be easy. thanks
./assets/js/script.js
./assets/img/myImage.png

Closing comment (2018-01-06T16:55:00Z): Yes, duplicate of #123
Repository: ng-packagr/ng-packagr

Issue #190: [PR WELCOME] Discover primary and secondary entry points from user configuration
Created: 2017-10-18T08:14:09Z
Type of Issue
[ ] Bug Report
[x] Feature Request

Description
Historically, a package.json and a ng-package.json are used to "configure" ng-packagr. The package.json is used for the module ID, npm metadata, and more node/npm-related things. The ng-package.json is used for destination paths, finding the entry file of an entry point, and angular/typescript/rollup-specific things.
Entry point discovery should be changed, see below. Discovery of primary and secondary entry points should both use this.
Expected Behaviour
New Draft / Outline (first one "wins"):

package.json: ngPackage
ng-package.json (requires a package.json as sibling)
ng-package.js (default export, requires a package.json as sibling)

Note: ignore package.json w/o ngPackage property.
Version Information
ng-packagr: v2.0.0-rc.0

Duplicate issue #213: BUILD ERROR if unrelated package.json exists in a sub-folder
Created: 2017-10-24T21:21:33Z
Type of Issue
[x ] Bug Report
[ ] Feature Request

Description
Added a folder called server at the root and containing a ten-line Express application and of course an accompanying package.json.  The ng-packagr build then immediately fails.
BUILD ERROR
Error File '/Users/admin/src/lytx/ngx/.ng_pkg_build/ngx-server/ts/server/public_api.ts' not found.
Error: Error File '/Users/admin
In fact if you delete everything in ./server except package.json you get this failure.
How To Reproduce
See description
Expected Behaviour
Ignore unrelated sub-folders.
Version Information
ng-packagr:  "^1.5.0-rc.0",

@angular: 4.2.4

Closing comment (2017-10-27T07:55:12Z): As a fix for the 1.5.0 feature release:

for auto-discovery of secondary entries, validate whether the package.json has a ngPackage property (can be an empty object)

For later releases, tracked by #190
Repository: nginx-proxy/acme-companion

Issue #376: Add support ECDSA certificate generation
Created: 2018-05-09T09:11:04Z
Currently JrCs/docker-letsencrypt-nginx-proxy-companion support only default RSA certificate generation.
It would be great if you could add support EC-256/EC-384 certificate generation.

Duplicate issue #466: Generate a ECDSA certificate?
Created: 2018-11-15T09:39:30Z
Is there a way to have my certificate be a ECDSA certificate? It's possible with let's encrypt.
There are many benefits, and I do not care about supporting old stuff. Also I'm optimizing for mobile first.
If possible, I'd like to have both ECDSA and RSA. Providing a solution that supports old and new clients, maybe could even be a default.
More info here: https://hackernoon.com/rsa-and-ecdsa-hybrid-nginx-setup-with-letsencrypt-certificates-ee422695d7d3
Thanks!

Closing comment (2018-11-15T10:26:10Z): Duplicate of #376
Repository: nginx-proxy/acme-companion

Issue #319: Support wildcard certificates with ACMEv2
Created: 2018-01-21T23:02:37Z
On January 27 letsencrypt will make star certificates fully available via the ACME v2 protocol.
Are you planning on adding support for this?

Duplicate issue #320: Wildcard Certificate
Created: 2018-01-22T12:33:54Z
Hi,
As you must know, Lets Encrypt will provide wildcard certificates from February, 27th. (It will requires DNS validation)
Does someone know if there's any ETA for when certifcates will be supported (If it will?)
More info: https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html

Closing comment (2018-01-22T12:34:27Z): Duplicate of #319
Repository: nginx-proxy/acme-companion

Issue #74: Proxy using wrong certificate
Created: 2016-06-23T11:08:43Z
I have multiple containers and if I open piwik.example.com, the certificate for pma.example.com is used.
But all other containers work correctly.
I start the containers like the following:
nginx-proxy
docker run -d -p 80:80 -p 443:443 \
    -v /srv/certs:/etc/nginx/certs:ro \
    -v /etc/nginx/vhost.d \
    -v /usr/share/nginx/html \
    -v /var/run/docker.sock:/tmp/docker.sock:ro \
    --name proxy --restart always jwilder/nginx-proxy

letsencrypt-nginx-proxy-companion
docker run -d \
    -v /srv/certs:/etc/nginx/certs:rw \
    -v /var/run/docker.sock:/var/run/docker.sock:ro \
    --volumes-from proxy \
    --name letsencrypt --restart always jrcs/letsencrypt-nginx-proxy-companion

piwik.example.com
docker run -d -e VIRTUAL_HOST=piwik.example.com -h piwik.example.com \
    -e LETSENCRYPT_HOST=piwik.example.com -e LETSENCRYPT_EMAIL=info@example.com \
    -v /srv/web/piwik/public:/var/www/html \
    --name site1 --restart always richarvey/nginx-php-fpm

pma.example.com
docker run -d -e VIRTUAL_HOST=pma.example.com -h pma.example.com \
    -e LETSENCRYPT_HOST=pma.example.com -e LETSENCRYPT_EMAIL=info@example.com \
    -v /srv/web/pma/public:/var/www/html \
    --name asd --restart always richarvey/nginx-php-fpm

If I open piwik.example.com in a browser, the certificate for pma.example.com is used, even if the container for site1 is not started 😟:
Images


Output of docker ps:

Duplicate issue #416: 503 for default or non-existent virtual hosts
Created: 2018-07-16T17:16:29Z
There should be a 503 or something, if a request comes in on a domain or IP address that is not defined by VIRTUAL_HOST env var. Instead, it just redirects to the first defined one.
According to this there must be a default added to the default listen-directive, for which I assume here is the right place. This file gets re-generated each time the proxy container starts though.
Is this within the scope of this project or rather upstream at jwilder/nginx-proxy?

Closing comment (2018-07-17T11:03:22Z): According to the answer from server fault that you quoted:

If you omit the default parameter, the first server block is treated as the default.

So this server block is already the default, being always the first.
I think your issue is instead yet another duplicate of #74, #373 and #411
If it is, could you close this issue and continue the discussion on #411 ?
Repository: nginx-proxy/acme-companion

Issue #242: Support for multiple nginx proxies
Created: 2017-07-25T11:14:57Z
Is it possible to combine multiple nginx containers with this letsencrypt image,
for example if i have multiple ipv4-adresses on a single docker-host?

Duplicate issue #171: unable to generate certs for second proxy
Created: 2017-02-15T10:42:57Z
I'm trying to run the jwilder/nginx-proxy twice, each with it's own dedicated IP.
For 'reasons' I cannot have the domains of proxy1 in the certificate of proxy2.
I modified the jwilder/nginx-proxy to look for VIRTUAL_HOSTS instead of VIRTUAL_HOST and run it as proxy2.
This set-up seems to work without issue.
The docker run for proxy1 looks as follows:

docker run -d -p ip.proxy.1:80:80 -p ip.proxy.1:443:443 --network isolated --name proxy 
-v /home/user/conf/htpasswd:/etc/nginx/htpasswd 
-v /home/user/certs:/etc/nginx/certs:ro -v /etc/nginx/vhost.d 
-v /home/user/conf/proxy1/cust.conf:/etc/nginx/conf.d/my_proxy.conf:ro 
-v /usr/share/nginx/html -v /var/run/docker.sock:/tmp/docker.sock:ro 
-v /home/user/logs/proxy/:/var/log/nginx/:rw jwilder/nginx-proxy

the docker run for proxy2 looks as follows:

docker run -d -p proxy.ip.2:80:80 -p proxy.ip.2:443:443 --network isolated --name proxy2 
-v /home/user/certs:/etc/nginx/certs:ro -v /etc/nginx/vhost.d
-v /usr/share/nginx/html -v /var/run/docker.sock:/tmp/docker.sock:ro 
-v /home/user/logs/proxy2/:/var/log/nginx/:rw proxy2

The docker run for the letsencrypt companion looks as follows:

docker run -d 
--name ssl 
-v /home/user/certs:/etc/nginx/certs:rw 
--network isolated 
--volumes-from proxy 
--volumes-from proxy2 
-v /var/run/docker.sock:/var/run/docker.sock:ro 
jrcs/letsencrypt-nginx-proxy-companion

I notice the 2nd proxy passes the .well-known request to the upstream.
In the upstream logs I get:

172.17.0.8 - - [15/Feb/2017:10:12:30 +0000] "GET /.well-known/acme-challenge/Umzbul_challenge_Mzb5v8E0Uk-ydRc HTTP/1.1" 404 169 "-" "Mozilla/5.0 (compatible; Let's Encrypt validation server; +https://www.letsencrypt.org)" "letsencrypt.ip"

in the proxy2 logs I get:

example.com letsencrypt.ip - - [15/Feb/2017:10:12:30 +0000] "GET /.well-known/acme-challenge/Umzbul_challenge_Mzb5v8E0Uk-ydRc HTTP/1.1" 404 169 "-" "Mozilla/5.0 (compatible; Let's Encrypt validation server; +https://www.letsencrypt.org)"

in the letsencrypt companion I get:

2017-02-15 10:12:30,075:ERROR:acme.challenges:256: Unable to reach http://example.com/.well-known/acme-challenge/Umzbul_challenge_Mzb5v8E0Uk-ydRc: HTTPConnectionPool(host='example.com', port=80): Max retries exceeded with url: /.well-known/acme-challenge/Umzbul_challenge_Mzb5v8E0Uk-ydRc (Caused by NewConnectionError('<requests.packages.urllib3.connection.HTTPConnection object at 0x7f1d056d9250>: Failed to establish a new connection: [Errno 113] Host is unreachable',))
2017-02-15 10:12:30,075:WARNING:simp_le:1303: example.com was not successfully self-verified. CA is likely to fail as well!

Is the letsencrypt companion able to serve 2 nginx-proxies or should I run it twice with some modifications?

Closing comment (2018-02-01T21:32:24Z): Duplicate of #242 so closing to have only one issue tracking this.
Repository: nginx-proxy/acme-companion

Issue #8: Self-signed for development
Created: 2016-01-13T22:17:49Z
I have some sites I want to migrate to HTTPS, so I want to work on them locally to make sure they work before moving the live sites.
If I use this container as part of my docker infrastructure, how do I use self-signed certs for my development environment?
Can I just create them and put them in the certs directory and everything will work?  Or will this container try to check them/renew them with ACME and blow up?
(I'm relatively new to working with HTTPS and trying to understand how to work with it.)

Duplicate issue #367: Certificates for local development domains (like *.test)
Created: 2018-04-21T09:56:09Z
Hi there, please, is there any way we can generate ssl certificates for local dev domains, like xxx.test (which are not reachable on the internet)? I can generate SSL certificates manually, but I don't like it :)
Thanx!

Closing comment (2018-04-25T07:09:50Z): Hi @maximkrusina
This is a duplicate of #8
@JrCs explained in that issue that he doesn't want to implement this feature on his project, I'll ask him if he'd reconsider, that seems like a good idea to me and not too hard to implement.
In the meantime you can use openssl from inside the container with docker exec, that's pretty straightforward and probably the easiest way for now.
Repository: nginx-proxy/acme-companion

Issue #277: TOS hash mismatch
Created: 2017-11-15T14:17:53Z
There is a new LE TOS, so the TOS hash is currently wrong, and failing.
https://letsencrypt.org/repository/

Duplicate issue #278: TOS hash mismatch
Created: 2017-11-15T14:42:03Z
Hello,
I see the previous issue, from 2016 that seems to be resolved.
But I am facing the same problem, using the last Docker version (17.10.0-ce, build f4ffd25) and the last image JrCs/docker-letsencrypt-nginx-proxy-companion.
I want to generate a new certificate, but there is an error: TOS hash mismatch. Found: cc88d8d9517f490191401e7b54e9ffd1a2b9082ec7a1d4cec6101f9f1647e7c.

Closing comment (2017-11-15T14:43:37Z): Hi @flexbrane - this is a duplicate of #277 - see the workaround & root cause identifier there.
Repository: nginx-proxy/acme-companion

Issue #275: Generate Certficate for non docker service
Created: 2017-11-12T19:05:32Z
Hello,
It would be nice to have a way to generate certificate for services running on host.
(via a configuration file for example)
Thanks

Duplicate issue #313: Feature Request: Ability to specify custom name of key file (other than key.pem)
Created: 2017-12-31T18:10:54Z
I would like to request the ability to specify a custom name for the various certificate-related files, specifically, the key file (key.pem).
I use this container with another container (jacobalberty/unifi) that expects the key file name to be privatekey.pem.
Thank you for providing a great container to make using Let's Encrypt certificates so easy!

Closing comment (2018-01-05T14:35:10Z): Thank you for the feedback. I did not realize that simp_le required the key to be named a certain way (I saw the file being passed as an argument to simp_le, therefore, I thought it would be a simple change).
I guess this issue is related to #275 in a way because the third-party application is not using the nginx proxy to provide the secure connection.
At this time, I did (manually) create a soft-link to provide the appropriate key file naming the third-party application expects. However, that soft-link will be destroyed once the certificate is renewed (because this container recreates (removes then creates) the entire directory instead of replacing the files within the directory).
Without creating a fork, I saw 3 options:

Ask the third-party application to allow for a custom name for the key file
Ask this project to allow for a custom name for the key file
Ask this project to introduce configurable event hooks (a la CertBot)

I figured option 2 was the simplest request and would provide benefit to the community (and I now understand why it cannot be done). I believe option 3 would provide the most benefit to the community but I figured that was a more significant request.
I understand that I could always go the fork route but I thought that there could be benefit to the community with a minor change.
Again, thanks for your feedback and thanks again for a great project.
Repository: nginx/docker-nginx

Issue #97: Any chance of alpine update to 3.4?
Created: 2016-06-08T15:22:31Z
Alpine 3.4 is out, and essentially just wondering if there is a time frame for updating the alpine image (at least the mainline one) to 3.4. I appreciate y'alls time!

Duplicate issue #117: Update mainline image to 1.11.3
Created: 2016-08-18T22:49:47Z
The current nginx mainline image version is 1.11.1 on DockerHub, but the latest Nginx is 1.11.3. This is probably a dupe of #88 practically, but we at least could use a refresh with the newest version of Nginx :).

Closing comment (2016-08-18T23:02:14Z): It is also a dupe of #97. The maintainer is currently on vacation.
Repository: nginx/docker-nginx

Issue #78: Alpine base cannot resolve links via DNS
Created: 2016-04-08T23:51:32Z
Apparently there is an issue with DNS resolution in alpine. See: https://forums.docker.com/t/container-link-problem-in-docker-cloud/6445/12. This prevents nginx images from resolving linked containers via DNS, such as on Docker Cloud.
Using alpine:edge will apparently fix the issue.

Duplicate issue #127: host not found in up stream
Created: 2016-10-23T07:37:12Z
I'm trying to run nginx as a reverse proxy inside docker. The issue is that nginx is exiting because it doesn't find the host in upstream (nginx strts faster than keycloak I assume) so it just exits.

docker compose

 version: '2'
 services:
  keycloak:
    image: jboss/keycloak-postgres
    ports:
      - "8080:8080"
  nginx:
    build:
      context: ./nginx
      dockerfile: dockerfile
    ports:
      - "80:80"
      - "443:443"
    depends_on:
      - keycloak
    entrypoint: ['sleep', '25']

 > nginx conf
  server {
    listen 80;

    location / {
      index index.html;
      root /usr/share/nginx/html;
    }

    location /auth {
      proxy_pass http://keycloack:8080/auth;
      proxy_set_header Host $host;
      proxy_set_header X-Real-IP $remote_addr;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Proto $scheme;
    }
  }

Closing comment (2017-04-12T13:32:10Z): If it was alpine, then it's related to #78
Repository: nginx/docker-nginx

Issue #262: It seems like nginx:latest is now broken
Created: 2018-08-29T09:16:03Z
When using nginx:latest to start a service on a Docker EE with Swarm worker nodes, the containers refuse to start. When using nginx:stable, everything works fine.
I believe this still worked yesterday, so it must be a recent change.

Duplicate issue #263: nginx:alpine not working
Created: 2018-08-29T10:16:43Z
My build using nginx:alpine are failing. Seems it failing for most of the tags saving few.

Closing comment (2018-08-29T10:22:09Z): Duplicate of #262
Repository: nginx/docker-nginx

Issue #262: It seems like nginx:latest is now broken
Created: 2018-08-29T09:16:03Z
When using nginx:latest to start a service on a Docker EE with Swarm worker nodes, the containers refuse to start. When using nginx:stable, everything works fine.
I believe this still worked yesterday, so it must be a recent change.

Duplicate issue #264: Not able to pull Nginx Docker images
Created: 2018-08-29T11:15:43Z
Not able to pull docker images of Nginx. I have tried to pull latest and alpine tags.
it looks like it is broken. i am getting the error 'no supported platform found in manifest list'.
please look into this

Closing comment (2018-08-29T11:25:46Z): Duplicate of #262
Repository: nginx/docker-nginx

Issue #141: Is it possible to copy the Nginx Dockerfile?
Created: 2017-02-01T22:06:57Z
Hey! We're building a complex Dockerfile that bases its installation of Nginx off of the stable Jessie build.
Recently, when the version was bumped up here, our docker builds began to break. I'm not too familiar with Jessie and apt-get, so I was wondering if someone knowledgeable here could help me understand if there's something I should modify in the Dockerfile to make it not be tied to the build here.
Just to be clear, literally copied the Dockerfile except we left out the CMD and the EXPOSE etc. The error we were getting had to do with installing nginx, with all the modules (nginx-module-xlst, nginx-module-geoip, etc.) suddenly having a hard dependency on the latest version of nginx (1.10.3 vs 1.10.2).
Thanks so much!

Duplicate issue #160: Nginx stable fails to build (1.10.3)
Created: 2017-04-18T15:48:39Z
With the following message:
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 nginx-module-geoip : Depends: nginx (= 1.12.0-1~jessie)
 nginx-module-image-filter : Depends: nginx (= 1.12.0-1~jessie)
 nginx-module-njs : Depends: nginx (= 1.12.0-1~jessie)
 nginx-module-perl : Depends: nginx (= 1.12.0-1~jessie)
 nginx-module-xslt : Depends: nginx (= 1.12.0-1~jessie)
E: Unable to correct problems, you have held broken packages.

Seems that the dependencies are broken.

Closing comment (2017-04-18T15:53:24Z): Duplicate of #141