![]() Host_ip should be the IP address of the server running stunnelĭestination_server_ip is the IP address of the server running whatever it is on an unusual port that can’t be accessed (obviously if the unusual port isn’t 8000 then change that too). keyout /etc/ssl/certs/stunnel.pem -nodes -x509 -days 365 Configuration fileĬreate a file /etc/stunnel/nf with contents like this: ![]() Sudo openssl req -new -out /etc/ssl/certs/stunnel.pem \ The installer doesn’t create any certificates, so you need to do this yourself: I used Ubuntu (12.04), so it was a simple matter of: You will needĪ box (VM) that you can install stuff on (with root access) beyond the firewall with an unblocked public IP that’s not already being used to host HTTPS – e.g. Having previously used stunnel to connect and old POP3 client to gmail I thought it would be able to help, and indeed it did. Npm ERR! Conflicting peer dependency: ERR! ERR! peer from ERR! node_modules/ngx-mdI recently came across a situation where somebody was trying to access an HTTPS service running on port 8000, which appeared to be blocked for them. Npm ERR! peer from ERR! node_modules/ngx-md Npm ERR! peer from ERR! ERR! from the root project Npm ERR! peer || ^14.0.0-0" from ERR! ERR! from the root project Npm ERR! While resolving: ERR! Found: ERR! ERR! from the root project It was almost too easy! npm ERR! code ERESOLVE While I did start off with many more errors than this and some were fixed by cleaning up my angular imports - in the end the final batch of errors shown here vanished by just removing ngx-md from package.json. And I'd managed to get away with it until now (I just reinstalled Windows and the latest node / npm brought me this issue). I once used ngx-md but (as you can see below) it wasn't updated since v8. You may have forgotten you even installed something that's breaking it. My tip is don't forget all the packages that may refer to Angular as well as the angular packages themselves. This problem can get very frustrating - I've spent a couple hours trying to understand it - even creating dummy angular 13 / 14 projects to see what the latest defaults are. I know that was a bad idea to use -force argument, but prefer to solve peer dependencies once angular is updated, not on each version. Npm ERR! C:\Users\leino\AppData\Local\npm-cache_logs\T16_41_50_262Z-debug.log Npm ERR! A complete log of this run can be found in: Npm ERR! See C:\Users\leino\AppData\Local\npm-cache\eresolve-report.txt for a full report. Npm ERR! to accept an incorrect (and potentially broken) dependency resolution. Npm ERR! this command with -force, or -legacy-peer-deps Npm ERR! Fix the upstream dependency conflict, or retry Npm ERR! Conflicting peer dependency: ERR! ERR! peer || ^11.2.0-next" from ERR! ERR! dev from the root project Npm ERR! While resolving: ERR! Found: ERR! ERR! dev from the root project ⠧ Installing packages (npm).npm ERR! code ERESOLVE Updating package.json with dependency karma "6.3.11" (was "5.0.9"). Package has an incompatible peer dependency to (requires "^8.0.0" (extended), would install "11.2.14"). Package has an incompatible peer dependency to (requires "7.x || 8.x" (extended), would install "11.2.14"). Installing a temporary Angular CLI versioned 11.2.18 to perform the update.įetching dependency metadata from registry. The installed Angular CLI version is outdated. Now I want to continue to Angular 11, 12 and 13 but when I use this command : npx update -force Then from Angular 9 to 10, same method with npx update -forceĪnd it works, too. So I use this command with -force argument : cmd /C "set "NG_DISABLE_VERSION_CHECK=1"
0 Comments
Leave a Reply. |