I tried to install ioncube on my Ubuntu server using the instructions available on the Internet, but despite all the steps, I was not able to set it up, and there is still an error that there is no ioncube on my browser. please guide me.
It should be noted that I use the Apache web server
enter image description here
Related
I've performed a clean install of Red5 Media Server 1.2.2 on Ubuntu Server 18.0.4 LTS.
I can access my server via <server ip>:5080. I see the screen confirming red5 is installed. If I click on demo followed by install, taking me to <server ip>:5080/installer, I get a 404 Error from Apache Tomcat.
What could I need to change, to access this page?
The installer webapp is not there anymore, that's why you get the 404. The app is no longer supported and as you've noticed, we haven't removed or fixed the link on the demo page yet.
ColdFusion 2016 stopped rendering website files in browser after I updated my Mac software to latest one, Mojave 10.14.1. Instead of seeing the rendered page in the browser I can see my repository files only.
I noticed that some previous settings regarding local server and Apache were removed after update. I did restore missing settings back how they were before and even reinstalled ColdFusion 2016, but still have that problem with rendering websites on the ColdFusion platform.
After running /Applications/ColdFusion2016/cfusion/runtime/bin and sudo ./wsconfig, I the get Web Server Configuration Window with content inside
[ localhost ] Apache : /private/etc/apache2.
Is there anyone who can help to resolve this issue please?
Change the directory to
/Application/ColdFusion2016/cfusion/runtime/bin
Run
sudo ./wsconfig
The documentation does not mention sudo, but I am suggesting it to be safe.
Source: https://helpx.adobe.com/coldfusion/configuring-administering/web-server-management.html
After testing ColdFusion 2016 platform using port :8500 I found out that CF server uses Tomcat path (wrong path) instead of Apache one (for Mac virtual directory file: httpd-vhost.conf) and both of them are running at the same time.
I am trying to install Prestashop 1.7 on an Ubuntu 14.04 LAMP droplet from Digitalocean.
After copying Prestashop source files under a presta folder in /var/www/html, when accessing http://95.85.6.69/presta/ in the browser I am getting redirected to http://95.85.6.69/presta/install/index.php?step=welcome which is cool, except, it keeps on redirecting until I am getting: ERR_TOO_MANY_REDIRECTS thrown back at me.
Am I doing something wrong? Is there a config I am missing? How can I surpass that error?
The image above is an addition to the error description.
P.S: Ignore the differences in IPs as they are the result of multiple deployments of the same snapshot, ubuntu 14.04 LAMP, on Digitalocean.
Have you enabled the curl extension? I had the same problem couple days ago. After investigating the problem, I found out that the curl extension wasn't enabled and Prestashop doesn't throw any errors if it is not enabled.
sudo apt-get install php5-curl
Then restart the apache2 server using
sudo service apache2 restart
Take a look at the following links, it might be possible that you find a solution for this problem:
https://forum.c4.cz/prestashop-1-7-0-4-instalace-a-chyba-too-many-redirects-t7692.html
https://serverfault.com/questions/824940/prestashop-1-7-too-many-redirects-on-frontend-shop
After installing PrestaShop on Ubuntu 18.04.4 LTS I had the same issue. Everything needed is installed and running. I checked the logs and there where no errors when loading the page, but the issue persisted.
I tried loading the Admin panel and was able to login. After reading in some simular issues I wondered if it had to do with SSL, that I set up with the domain.
Long Story short, if you can reach the admin panel check the shop settings and if SSL is aktivated and is aktivated for all pages. That solved the issue for me.
The Issue:
I've recently been working enabling HTTP/2 for a large PHP+JS application (generally a Backbone-based SPA served by a PHP back-end). While most resources load fine, two requests are getting stuck in the "Stalled" state for exactly 5 minutes before resolving and downloading as normal.
The two request in question are a simple XMLHttpRequest to our back-end and a request for a Font Awesome font file. Other font files and back-end requests are loaded just fine, but these two will consistently hang up when HTTP/2 is enabled.
Debugging Information:
Here are the headers associated with the font file request listed in Chrome's dev tools:
...and here's the output from chrome://net-internals, with the hangup occurring at HTTP_TRANSACTION_READ_HEADERS (see the dt of almost 30000ms):
Further Details:
This application is served using a build of apache2 that includes the mod_http2 module rather than the standard version of apache2 that is packaged with Ubuntu. The same behavior is reported in the latest versions of Firefox, Chrome, and Chrome beta on Ubuntu 16.04.
For the sake of local development, all SSL is being run through a self-signed OpenSSL certificate, generated with OpenSSL version 1.0.2j.
It should also be noted that all other successful requests are running through Backbone-related methods, which delegate to jQuery's $.ajax, where the failed XMLHttpRequest is using the native JS XMLHttpRequest Object.
Thanks for your help.
What version of Apache and mod_http2 are you using?
There's been a load of fixes for this sort of thing and Apache 2.4.25 is about to be released including those fixes, so suggest you upgrade to that when it comes out in next day or two and try again.
Alternatively, if you don't want to wait, you can try updating mod_http2 independently by doing the following (assuming Apache is installed in /usr/local/apache2/ but adjust that as appropriate):
#Download and install mod_http2 outside of a regular Apache release
#Latest version is here: https://github.com/icing/mod_h2/releases/
wget https://github.com/icing/mod_h2/releases/download/v1.8.3/mod_http2-1.8.3.tar.gz
tar -zxvf mod_http2-1.8.3.tar.gz
cd mod_http2-1.8.3
./configure --with-apxs=/usr/local/apache2/bin/apxs
make
sudo make install
Then restart Apache and confirm from error log that you are running mod_http2-1.8.3.
If that doesn't work then raise an issue here: https://github.com/icing/mod_h2/ as the mod_http2 developer (#icing) is very responsive to issues. Assuming this is an Apache bug of course.
I have installed Red (setup-Red5-1.0.0-RC2-java6) on my windows xp. Red5 server running proper. but installer.swf not able to connect. also getting 404 error while installing demos. demos directory is not at the location as well.
any Idea what could have cause this ?
Try using the 0.9.1 build. Also your firewall should allow listening on port 5080 (default for red5).
As an alternative try manually installing the demos from the source trunk and restart the server.