Node.js express-admin "connect ECONNREFUSED" - mysql

I'm trying to get a nice admin GUI for databasing for node.js like you get from phpmyadmin.
That's where I found express-admin.
http://simov.github.io/express-admin-site/
I follow their instructions and installed it with no problem. When I ran the app.js I entered in my credentials, "database type", "database name", etc. I choose the default port 3000 and after I was finished I received "connect ECONNREFUSED", nothing more. I tried different ports and even copy pasted the .json file they provided in the tutorial. nothing seemed to work.
I have no problem hosting my application I have been working on so I don't believe it's the port.. [and no I was not hosting my application as the same time]
Thank you guys I hope to get some feedback! (:

Max, I'm the author of express-admin.
I just stumbled upon your question here. Even though a month have passed if you are still experiencing problems configuring the admin you can open up an issue here: https://github.com/simov/express-admin/issues (I get notified via email when someone opens up an issue there).
Also you should provide a more detailed information about your server/database set up + the full error message.

Related

Unable to fix malformed JSON in wordpress

I am using woocommerce for the first time with wordpress in order to setup an e-commerce site. Everything is installed properly from wordpress to woocommerce plugin and the theme. But the problem resides.
Kindly check below image
I keep getting the same error again and again, I reinstalled the entire wordpress site but no luck. I followed few tutorials wherein they instruct to open browser console and check for a red line which I don't receive in my console.
What I get is in the image below
Also, somehow I am not even able to select another payment option other then cash on delivery which I have installed on my site. I have been struggling for last 3 days, but no luck! Kindly do not down vote this question. As I am feeling helpless at the moment.
The site is fashionburst.in
Thanks in advance
For anyone who might run into this issue, try to turn on debugging in wp-config.php
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
And then read the log file in wp-content/debug.log. I had a PHP error in one of my plugin's hooks and since the checkout is processed with JS, the checkout.min.js threw this error. Log file should give you proper error report (in my case I was using undefined PHP function).

Attackers might be trying to steal your information from (for example, passwords, messages, or credit cards). NET::ERR_CERT_COMMON_NAME_INVALID

I'm getting the following error for one specific website (and only one specific website):
I've tried the following:
Making sure my time / data settings are correct
Clearing all browsing data
Deleting and reinstalling Chrome
Nothing works. Interestingly, I only get this error for one specific site (www.datacamp.com). And when I turn off wi-fi and tether my iPhone, I'm able to get through to the site. When I turn my wi-fi back on, I get errors again.
When I view details I see this:
And when I view the certificate I see this:
I've tried deleting the certificate, but I get the following message:
Any help is greatly appreciated!
If you are getting this error when access localhost, simply go to
chrome://flags/
and enable Allow invalid certificates for resources loaded from localhost.
Ok, I don't know why it took me so long to try this. I just unplugged my modem and router, then plugged them back in. At least for now, it seems to have resolved the issue...
Check your connection's DNS entries. It's likely a adware or malware program modified them.
open network and sharing center
On the left side- click on:
change advanced sharing settings.
click on home or work.
go through and check "turn off" for the first three questions.
turn on password.
Your computer connection was wide open!!!!
Flushing DNS worked for me in Windows 10. Simply open powershell and issue this command:
ipconfig /flushdns
Adding Google DNS 8.8.8.8 and the Cloudflare DNS 1.1.1.1 solved my issue.
If you are facing this while visiting a website, you can follow below.
This might not solve the issue always. But, this is how I solve it around 8/10 times.
To Resolve this on Chrome :
[Approach 1]
Just Click on Proceed to www.xyzxyz.com..(unsafe)
[Approach 2]
Go to : chrome://net-internals/#hsts
Suppose the site for which the error shown is : https://twitter.com/xxx/yyy....
In the "Delete Domain" option, Enter domain as "twitter.com".
Press Delete.
Reload the page you were trying to visit.

Chrome basic authentication custom message stopped working

I am using nginx proxy to server my web-page. For login user need to provide his 2 factor authentication code and his password, to let users know that they need to enter their password+2 factor code to login, I send them a message "Login required, username, password+VIP token"'
And this what I get now
This has stopped working from Chrome version 49. I am on 49.0.2623.110.
Any work around to fix this? It works perfectly on firefox.
This was indeed answered in Change Basic HTTP Authentication realm and login dialog message.
Short explanation: You were actually defining realms with auth_basic directives of Nginx on the server side. But "whether to prompt this message or not" is basically a design choice made by specific client programs. And Chrome just chose to hide it, for reasons you may find in the first link.
In fact, as of my decade (2022), Firefox seems to hide the message too.
Why I necromance this very old post: I was reading this documentation of Nginx. At the end of the article, there is a screenshot similar to the Firefox one in the OP. Unsurprisingly, my browser didn't behave like that even I followed all the instructions therein. Then I started Googling and this is the first hit relevant to my question. After I learned something about HTTP basic authentication, realm etc and finally came across the first link, I think I should post something here.
Apparently, Nginx documentation is using kinda modern UI to host kinda outdated contents. Hope this answer will help anyone who is confused by that screenshot too ;)

ibm connections adding a library to comunity

Im trying to make connections 4.5 working with content manager. I guess im quite far away from start finally but there are many things i need to fix.
Sometimes my widgets just doesnt load. It says cannot load widgets-config.xml
when i restart deployment and appsrv everything looks good.
My biggest problem is to add library to community. Because i want to see how workflow works and the id like to create linked library of this. This is what i get when i try to add library widget to the community (linked library widget works well)
CLFWZ0004E: Event 'widget.added' sent to remote lifecycle handler at https://conserv.egroup.local/dm/atom/communities/feed returned bad response: 403 - Forbidden
I guess there is som problem with https access. Can anybody of you guys ever faced this problem? Some hints?
UPDATE-1
After accessing that page from it gives me this :
<td:error>
<td:errorCode>UnsupportedOperation</td:errorCode>
<td:errorMessage>CQL5602: The attempted operation, GET, is not allowed on the resource /communities/feed.
Contact your administrator and provide the incident ID: 1381320497551.
The administrator should forward this information to the application owner.
</td:errorMessage>
</td:error>
So i guess maybe there can be som problem with proxy policies. I tried to make some changes with changes default policy url to *. But still no progress..
Hints?

Pywikibot Error "Warning: Token not found on Example:de. You will not be able to edit any page"

I tried to install Pywikibot. So far so good, the bot is able to log in, apparently access api.php, but when I want to run a script it says:
Warning: Token not found on Example:de. You will not be able to edit any page
I tried to search on the web, but either I am not looking well enough or there just isn't anybody with my problem.
I faced the same error when server name was change. So, check hostname in your family file. However, I'm not sure it is your case because you was able to login. But may be it will help someone with similar warning message.