It looks like trial server was updated with the brand new 7.6 convertigo version.
.
My app (convertigo 7.5.6) on trial doesn't work anymore because (it looks like) convertigo is looking for couchDB server on 127.0.0.1 local ip adress.
Do I have to upgrade my app into 7.6 version ? Or what sould I do to make it work as-is on trial ?
Thank you
Thanks for reporting. Our CouchDB server was out.
Now it is up again, can you confirm this is ok for you ?
Related
My first time coming to Centos Panel.
I started moving my websites from cyberpanel. However, bringing the old website's data over is difficult. Specifically I uploaded the SQL and the Plulic hml. Then I changed the DB_NAME, DB_PASSWORD, DB_HOST values but the website didn't work.
I see the old DB_HOST is localhost:3306 is there any problem?
I also tried a fresh install of Wordpress and the site works.
I have a virtual machine running Ubuntu 16.04 and I have downloaded Apache Zeppelin 0.7.0. The problem that I am facing is that when I try to start the Zeppelin server using bin/zeppelin-daemon.sh start it says ok but I cannot access it from the browser(using the default localhost:8080). If I run bin/zeppelin-daemon.sh status it says that the server is already running.
Also, I tried to start the server using bin/zeppelin.sh and this time some information is displayed in the terminal but with no effect.
Any idea will be highly appreciated.
Thank you!
I had the same issue. I was getting errors in my browser console like the screenshot below.
After cleaning the cache, it works.
Following the tutorial from their website (link) I managed to run it. This implies building it from sources. Also, I had to wait a couple of minutes before the zeppelin was available at localhost:8080 (even though in the terminal "server started [OK]" was displayed
[Icant able to connect to the server using zeppelin notebook Can any tell me the solution
I tried to set up WordPress under Google App Engine earlier tonight (following the instructions here: https://developers.google.com/appengine/articles/wordpress).
It runs fine locally, but when I push to remote I get a database error (visible at https://wp-dot-frontiermediag.appspot.com/). If we throw on a /wp_admin/install.php you get:
This either means that the username and password information in your
wp-config.php file is incorrect or we can't contact the database server
at :/cloudsql/frontiermediag:fmwp. This could mean your host's database
server is down.
Here's the relevant code in wp-config:
/** MySQL hostname */
if(isset($_SERVER['SERVER_SOFTWARE']) && strpos($_SERVER['SERVER_SOFTWARE'],'Google App Engine') !== false) {
define('DB_HOST', ':/cloudsql/frontiermediag:fmwp');
}else{
define('DB_HOST', 'localhost');
}
frontiermediag:fmwp is showing "Status Runnable" in Developers Console > Cloud SQL.
I did this once before and it worked so I'm not sure what I'm missing here. I thought it might have been because I'm using WP 3.8.1. but rolled back to 3.5.1 and same thing's happening.
Any ideas? frontiermediag is listed as an authorized application on the :fmwp ACL.
This situation happened to me earlier.However, I edited my Cloud SQL instance , and set "Preferred Location" as "Follow App Engine App" from Google Developers Console. This database connection problem was solved in my case.
I tried the instructions with wordpress 3.5.1 and the instructions seem to work for me. The code snippet you have above seems right and I am not sure what could be wrong without looking at rest of your code. Can you try the instructions from the beginning one more time with 3.5.1?
I had this issue, because "Follow App Engine App" doesn't seem to be an option for second generation instances in my case, and so the instance connection name includes the region setting.
Look at the instance details, and under properties, find "Instance connection name". That is the text that should follow :cloudsql/.
I jus installed Solr 4.2 on my local computer using port 8080 and test ok with url http://localhost : 8080/solr/, then I share this to my colleagues with url http://10.18.59.179:8080/solr/ where 10.18.59.179 is local ip of my company. However my colleague (his ip is 10.18.59.105) told me, the admin main page just shows 'loading...' and hang there. I've installed solr 3.3 before and they can connect to admin page on my computer correctly. What's wrong with Solr 4.2's admin page?
Solr 4.2 code is a tested and working stable release. If you can reach its admin page but someone else can not reach it, the first thing to check it does another machine has right to reach your computer.
In my case, any browser will show 'loading...' forever. The reason, again in my case, is I started Solr 5.2 with a typo in ZooKeeper switch. It should be "-z localhost:2181,localhost:2182,localhost:2183" but I had "-z localhost:2181,localhost2182,localhost:2183". After adding the ":", everything started working again.
Im really having a problem with this one. My server is a linux CentOS based running Plesk 9.2
After the update my email forwarding stopped working! Plesk uses qmail to manage emails. Basically whatever I do in the webpased Plesk panel just does not work with email forwarding. Does anyone know what can be the problem and how can I fix it?
I wish, haveing a similar problem but with and older version of plesk. After I rebuilt the qmail queue email redirection stoped working. Strange because everything looks fin in the psa mail log