-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running the webinterface on another port #20
Comments
Hi, The web UI does not include a dedicated HTTP server, it is simply served by the same server which served your PHP application. Have you tried opening |
Hmm, yeah i tried, i can only run it from my host machine (its an vm), and apache is just serving the vhost bound. When i run it with lynx from the console i get an 404. |
You should check your client ip |
I'll doublecheck that, since i did put my ip in the whitelist, but perhaps i made a typo. Ill get back to you. |
You may be interested by last revision of master which include some useful logs (in nginx error log or fpm error log) in case web ui access failure. See #23 |
Ah cool, tomorrow i have some time to check it out again. :) |
Well, still not doing what it should really. I've build the current master. Config file
Apache log when trying to connect:
|
And th elocation of spx.ini. (apache has been restarted also)
|
Hmm, could it be Apache is just not supported? :x |
Yes it is possible. I'll try with apache2 this evening. |
@bbrala I've an issue with apache2 / mod_php 7.0, web UI HTTP responses are ill-formed (see below). I'll fix it in a few days.
|
Thanks :) |
I've got same result on |
I tried again in master, unfortunately, it is still nog working. Commandline is fine, but through apache still gives an 404. |
Hum, it's look like to work for my configuration ( RUN set -xe \
&& cd /tmp \
&& git clone https://github.com/NoiseByNorthwest/php-spx.git \
&& cd php-spx \
&& phpize \
&& ./configure \
&& make \
&& make install \
&& echo "spx.http_enabled=1\nspx.http_key=\"dev\"\nspx.http_ip_whitelist=\"127.0.0.1,172.123.0.200\"\nspx.http_ui_assets_dir=/usr/share/misc/php-spx/assets/web-ui\nextension=spx.so" > /etc/php5/mods-available/spx.ini \
&& php5enmod spx |
But, for projects working on Laravel, I've got a 301 loop redirections HTTP/1.1 301 Moved Permanently
Server: nginx/1.12.2
Date: Mon, 19 Mar 2018 09:41:03 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Location: /_spx/?SPX_KEY=dev
Vary: Accept-Encoding HTTP/1.1 301 Moved Permanently
Server: nginx/1.12.2
Date: Mon, 19 Mar 2018 09:42:07 GMT
Content-Type: text/html; charset=iso-8859-1
Connection: keep-alive
Location: http://xxx/_spx?SPX_KEY=dev
Vary: Accept-Encoding The first tries to append the ending Logs from
Logs from Apache2
Edit: it seems the |
@cmizzi OK I just see the .htaccess used by Laravel https://github.com/laravel/laravel/blob/master/public/.htaccess#L12 Is |
@bbrala Can you provide SPX notice logs ? (those starting with "SPX: access") |
@NoiseByNorthwest This seems to work. I would be great to redirect on it, I don't think I'm not the only one with this issue. I didn't try directly in |
@cmizzi done on master (redirection to .../index.html) |
What do you mean with the SPX notice logs? |
This kind of log I do not reproduce the apache2 bugs since merge of #34. So you have to help me by trying the urls listed in my previous comment and giving me back the response headers & spx notice logs. Can you aslo give me your apache2 vhost setup & .htaccess ? |
In my case it also doesn't work. I use:
Everything is correctly installed. I use PHP fpm and Nginx. But the point is that I have a default fallback server configuration in Nginx, to catch all domains that aren't matching any of my server name configurations. Hence the reason I think I just get my fallback URL, this localhost will never work in my Nginx setup:
Such a server config may look like this:
|
Hi,
I was trying to get this working on my dev env, but i can't reach the webinterface. Is there a possibility to run it on a different point so it doesn't conflict with apache?
Regards,
Bjorn.
The text was updated successfully, but these errors were encountered: