Forum Replies Created
-
Posts
-
This is a dedicated server. I control it. No support. That is why i use plesk.
What does not make any sense is that i have installed and removed other packages on the server and have not had any problems. Those apps ran listening on ports. Ie voip etc.
Looking over a dozen sites explaining npm simple install i see others having issues with puppeteer recent version.
What are you running?
-
Thank you for the notes.
After npm -g install puppeteer, seems it did not complete something but I don’t know what that is.
If I try to run one of the puppeteer examples/screenshot.js from the examples dir it fails in both
wpterm and linux term thro same error
$ node screenshot.js
node:internal/modules/cjs/loader:928
throw err;
^Error: Cannot find module ‘puppeteer’
-
Ok thank you. The plesk stuff seems to be oriented around the node express server and not a node library, like puppeteer.
So I have done npm install -g puppeteer
~#npm -g list
/usr/lib
├── n@7.0.0
├── npm@7.4.0
└── puppeteer@5.5.0So when I install your rss to url plugin it will immediately be able to use puppeteer without doing anything else?
thank you
-
-
-
-
Well This is were you need to determine the problem not me.
We are getting to the spinnerchief server
the correct api, user and password was used. Not AAAA, UUU and PPP shown was not sure if this a public thread.
server: cat /etc/centos-release
CentOS Linux release 7.8.2003 (Core)curl -v http://api.spinnerchief.com:443/apikey=AAAAAAAAA&username=UUUU&password=PPPPPPP&spinfreq=2&Wordscount=6&wordquality=0&tagprotect=%5B%5D&original=0&thesaurus=English&replacetype=0&chartype=1&convertbase=0
[2] 47713
[3] 47714
[4] 47715
[5] 47716
[6] 47717
[7] 47718
[8] 47719
[9] 47720
[10] 47721
[11] 47722
[12] 47723
[7] Done wordquality=0
root@cngidev:~#* About to connect() to api.spinnerchief.com port 443 (#0)
* Trying 47.90.207.195…
* Connected to api.spinnerchief.com (47.90.207.195) port 443 (#0)
> GET /apikey=AAAAAAAAAAAA HTTP/1.1
> User-Agent: curl/7.29.0
> Host: api.spinnerchief.com:443
> Accept: */*
>
* Empty reply from server
* Connection #0 to host api.spinnerchief.com left intact
curl: (52) Empty reply from server
^C -
I believe your need to explicitly assign port 443 and not use https
see doc
https://developer.spinnerchief.com/API_Document.aspx
Tested this:
curl http://api.spinnerchief.com:443
curl: (52) Empty reply from servercurl https://api.spinnerchief.com:443
no reply on https
-
I can’t reach https://api.spinnerchief.com from any server or client.
curl -Is http://account.spinnerchief.com/Login.aspx
HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 7232
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/7.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Tue, 29 Sep 2020 17:42:22 GMTI can reach this url from any server or client? Can you find out from the dev site if the https://api.spinnerchief.com is correct?
-
I see no response and 1 response on this test.
root:~#curl -Is https://api.spinnerchief.com | head -n 1
^C
root:~#curl -Is http://www.google.com | head -n 1
HTTP/1.1 200 OKI’ll try to find out why. thank you
But if you could provide an example curl cmd that your software uses I can get a valid test.
thank you
-
