I am trying to install visual plug in for my wiki.
during installation i marked nearly all plugins and the result is all available after start.
But i can not save a page via visual.
Because parsoid did not started after installation.
So i decided to install parsoid my self via npm.
I started parsoid now the problem is:
Error contacting the Parsoid/RESTBase server (HTTP 401)
at the same time on the parsoid termina i see the following lines:
at Request._callback (C:\Users\baran\node_modules\parsoid\lib\mw\ApiRequest.js:332:35)\n at Request.self.callback (C:\Users\baran\node_modules\parsoid\node_modules\request\request.js:185:22)\n at Request.emit (events.js:315:20)\n at Request. (C:\Users\baran\node_modules\parsoid\node_modules\request\request.js:1157:10)\n at Request.emit (events.js:315:20)\n at IncomingMessage. (C:\Users\baran\node_modules\parsoid\node_modules\request\request.js:1079:12)\n at Object.onceWrapper (events.js:421:28)\n at IncomingMessage.emit (events.js:327:22)\n at endReadableNT (_stream_readable.js:1327:12)
\n at processTicksAndRejections (internal/process/task_queues.js:80:21)","httpStatus":401,"levelPath":"fatal/request"},"msg":"Your
wiki requires a logged-in account to access the API.","time":"2020-11-17T16:21:29.965Z","v":0}
So the critical line is:
Your wiki requires a logged-in account to access the API
I have installed wiki and parsoid separately how could i enable parsoid to login to the wiki ? ?
Thanx
It is not the correct solution but it is possible to set wiki as "not private" so no need for login for parsoid, and you can protect pages that you don't want other users to modify.
Related
I am trying to create a serverless project. But it gives an error when giving the serverless command on the cmd. Please help me to solve this.
first I installed the serverless with 'npm install -g serverless' command. Then I gave 'serverless' command. So following error was displayed on the cmd.
C:\Geethma\myFiles\serverlessTutorial>serverless
Creating a new serverless project
? What do you want to make? AWS - Node.js - Starter
? What do you want to call this project? aws-node-project
Environment: win32, node 16.15.0, framework 3.18.2, plugin 6.2.2, SDK 4.3.2
Docs: docs.serverless.com
Support: forum.serverless.com
Bugs: github.com/serverless/serverless/issues
Error:
RequestError: self signed certificate in certificate chain
at ClientRequest.<anonymous> (C:\Users\geethma.rathnayake\AppData\Roaming\npm\node_modules\serverless\node_modules\got\dist\source\core\index.js:962:111)
at Object.onceWrapper (node:events:642:26)
at ClientRequest.emit (node:events:539:35)
at ClientRequest.emit (node:domain:475:12)
at ClientRequest.origin.emit (C:\Users\geethma.rathnayake\AppData\Roaming\npm\node_modules\serverless\node_modules\#szmarczak\http-timer\dist\source\index.js:43:20)
at TLSSocket.socketErrorListener (node:_http_client:454:9)
at TLSSocket.emit (node:events:527:28)
at TLSSocket.emit (node:domain:475:12)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
at TLSSocket.onConnectSecure (node:_tls_wrap:1532:34)
at TLSSocket.emit (node:events:527:28)
at TLSSocket.emit (node:domain:475:12)
at TLSSocket._finishInit (node:_tls_wrap:946:8)
at TLSWrap.ssl.onhandshakedone (node:_tls_wrap:727:12)
If you're using a machine provided by an employer, they may have installed self-signed SSL certificates in order to connect to internal systems or run fleet management software.
You can override strict checking in Node by either prepending the command with NODE_TLS_REJECT_UNAUTHORIZED=0 serverless, or permanently with npm config set strict-ssl false.
I had checked with Aaron's answer, but it didn't work for my case.
Issue on my side was with my company's VPN, as it was blocking sending/receiving the data. I went with the below steps that solved my issue.
Solution
Try disabling the VPN.
Run the command again.
Verify if it works.
Also make sure that your IAM user has necessary privileges to perform this by attaching necessary policy in the AWS's IAM User page.
I have trawled the net on this one and cannot find a resolution.
I have deployed an EC2 instance from a AWS RHEL 8 AMI.
I have installed all the pre-requisites for aws-azure-login but cannot connect to my accounts over SAML. (https://github.com/sportradar/aws-azure-login)
The config file has been created with parameters. When running aws-azure-login it returns the username, I press enter and then it hangs for minutes and returns the following error:
Unable to recognize page state! A screenshot has been dumped to aws-azure-login-unrecognized-state.png. If this problem persists, try running with --mode=gui or --mode=debug
After running in debug i get the following output:
Logging in with profile 'default'...
Using AWS SAML endpoint https://signin.aws.amazon.com/saml
Error: Failed to launch the browser process!
[13527:13527:1220/050718.762168:ERROR:browser_main_loop.cc(1409)] Unable to open X display.
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
at onClose (/usr/lib/node_modules/aws-azure-login/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:197:20)
at Interface.<anonymous> (/usr/lib/node_modules/aws-azure-login/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:187:68)
at Interface.emit (events.js:412:35)
at Interface.emit (domain.js:475:12)
at Interface.close (readline.js:530:8)
at Socket.onend (readline.js:254:10)
at Socket.emit (events.js:412:35)
at Socket.emit (domain.js:475:12)
at endReadableNT (internal/streams/readable.js:1334:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
Node version = v14.18.2
Any pointers would be greatly appreciated.
Note: on Linux you will likely need to disable the Puppeteer sandbox
or Chrome will fail to launch:
aws-azure-login --no-sandbox
If not check Unable to open X display when trying to run google-chrome on Centos (Rhel 7.5)
I bumped into same issue on CentOS7
aws-azure-login --profile <profile_name> --no-prompt --no-sandbox --enable-chrome-network-service --no-verify-ssl
worked for me, hope I helped anyone
I was getting the same error but then I end up recreating a new profile name. This time, I made sure that my profile name was one word, all lower case, and only characters was used. Example: automation
Usually when I start my web application, the browser will open https://localhost:44305
But I want to reach the site from my phone. I've tried changing the applicationhost configfile, firewall inbound rules and all that. But then I found this little thing iisexpress-github
I type this in my console: iisexpress-proxy https://localhost:44305 to 3005
Which results in this line: Proxying https://localhost:44305 to network interfaces:
Ethernet: 192.168.10.41:3005
Listening... [press Control-C to exit]
After following instructions, the browser gives following error: 'Aw snap! Something went wrong. Check your console to see the error.'
And then I look at my console which says the following:
Error: unable to verify the first certificate
at Error (native)
at TLSSocket.<anonymous> (_tls_wrap.js:1016:38)
at emitNone (events.js:67:13)
at TLSSocket.emit (events.js:166:7)
at TLSSocket._finishInit (_tls_wrap.js:585:8)
Usually my site is https, but this seems only to proxy to normal http.
What to do?
InternalOpenIDError: Failed to verify assertion
at /var/nodejs/Website/node_modules/passport-openid/lib/passport-openid/strategy.js:184:36
at /var/nodejs/Website/node_modules/openid/openid.js:927:12
at /var/nodejs/Website/node_modules/openid/openid.js:1051:16
at /var/nodejs/Website/node_modules/openid/openid.js:1169:16
at Request._callback (/var/nodejs/Website/node_modules/openid/openid.js:190:7)
at Request.self.callback (/var/nodejs/Website/node_modules/request/request.js:198:22)
at emitTwo (events.js:87:13)
at Request.emit (events.js:172:7)
at Request.<anonymous> (/var/nodejs/Website/node_modules/request/request.js:1035:10)
at emitOne (events.js:82:20)
GET /auth/steam/callback?openid.ns=http%3A%2F%2Fspecs.openid.net%2Fauth%2F2.0&openid.mode=id_res&openid.op_endpoint=https%3A%2F%2Fsteamcommunity.com%2Fopenid%2Flogin&openid.claimed_id=http%3A%2F%2Fsteamcommunity.com%2Fopenid%2Fid%2F76561198197967283&openid.identity=http%3A%2F%2Fsteamcommunity.com%2Fopenid%2Fid%2F76561198197967283&openid.return_to=http%3A%2F%2Fcsgomayhem.com%2Fauth%2Fsteam%2Fcallback&openid.response_nonce=2015-11-25T18%3A40%3A44ZOdgvGQXoVnz9LWfko54I371tMOM%3D&openid.assoc_handle=1234567890&openid.signed=signed%2Cop_endpoint%2Cclaimed_id%2Cidentity%2Creturn_to%2Cresponse_nonce%2Cassoc_handle&openid.sig=L5jXiwo2S4mVe0r%2BkcpU%2Bj%2BaEEU%3D 500 665ms - 708b
I've had my code working for several weeks now in my windows dev environment but now trying to run it on an Ubuntu 14.04 prod machine I am presented with this error when authenticating someone through Steam. I have no idea what the error means and Googling and searching on here hasn't yielded any results. I can provide the relevant code if you tell me what I'm looking for or if this is an easy fix please let me know.
All help would be greatly appreciated, regards.
I solved this by downgrading my version of passport as if appeared to be incompatible with passport-steam. I see some examples for authentication on the github of passport-steam if you ever need if for just authenticating users but not getting their details.
I am getting this error when trying to create a message on a queue in azure using node.js azure package version 0.6.6: {"code":"ECONNREFUSED","errno":"ECONNREFUSED","syscall":"connect"}
It only happens in the deployed WebRole, but works fine locally and in Azure websites. I need this to be in a webrole as I need to have an SSL certificate.
I deployed the role using this method: https://www.windowsazure.com/en-us/develop/nodejs/tutorials/getting-started/
An error I see in the logs is this which may help diagnose.
Application has thrown an uncaught exception and is terminated:
TypeError: Cannot read property 'statusCode' of null
at E:\approot\node_modules\azure\lib\services\queue\queueservice.js:295:54
at Request._callback (E:\approot\node_modules\azure\lib\services\core\serviceclient.js:197:9)
at E:\approot\node_modules\azure\node_modules\request\main.js:122:22
at Request.<anonymous> (native)
at Request.emit (events.js:67:17)
at ClientRequest.<anonymous> (E:\approot\node_modules\azure\node_modules\request\main.js:224:10)
at ClientRequest.emit (events.js:67:17)
at Socket.socketErrorListener (http.js:1188:9)
at Socket.emit (events.js:67:17)
at Array.0 (net.js:301:14)
I got the answer from posting an issue on the github repo here:
https://github.com/WindowsAzure/azure-sdk-for-node/issues/434
Answer:
I removed the EMULATED env var from web.config before I published. There was a bug (fixed in the 0.6.7 release) that prevented replacing web.cloud.config for web.config
Thanks markcowl!