Jump to content

YPCrumble

Approved members
  • Content Count

    8
  • Joined

  • Last visited

  1. @andrewatfornax haha that's completely understandable! I'm coming back to my adserver in ~February so will respond then.
  2. Hey @andrewatfornax thanks for your note! I am sure I am confusing these endpoints. I'm also happy to start documenting the API and sending you a text file (or markdown?) is fine. > AFAIK - you probably need to generate a valid XML request that defines the API action you are looking to perform... I'm looking into generating a valid XML request. As I get started, is there a particular part of the codebase you could point me to where the XML endpoints are written? EDIT: I see that prime just mentioned /www/api/v2/xmlrpc/index.php - that's what I was looking for. There I see what looks like routes for (what appears to be) endpoints like `ox.logon`. What would be helpful is an explanation of how one of these endpoints works. Once I get one, I'm sure the rest would be easy to grok. For instance, would I create an XML request to: http://localhost:8080/www/api/v2/xmlrpc/ox.logon ? (I doubt this is correct, but I think it explains what I mean).
  3. UPDATE: the issue was my permissions on my revive-adserver folder. I was installing them with 644 permissions rather than 700 into `/var/www/html`. By changing back permissions to 700 the redirect stopped. Hopefully this helps someone in the future. @Matteo do you happen to understand why the improper permissions might have caused this redirect, or which code is likely the source of the redirect? I'd love to submit a PR that causes Revive to fail loudly in the event that permissions are improperly set on its source files. That would have made this redirect issue much easier to debug.
  4. I figured out the issue. I'm not 100% sure the cause, but I had to completely rebuild my MySQL server and it worked fine. Previously I had just just been rebuilding my Revive server. Perhaps there was a redirect issue due to a cached response from the MySQL server? Matteo, in any case thank you for your help!
  5. Yes - this is because I'm using Docker. The PORT setting for Docker is simply 443/tcp, 0.0.0.0:8080->80/tcp I don't think it's a Docker issue however, because NGINX works fine - like I said if I replace the `index index.php` directive with a simple static index.html file, it gets served no problem at localhost:8080 on my machine.
  6. Thanks for your answer! Yes, this is a brand new install, and yes I'm trying to install it right now. I'm installing it on my own localhost - I should be able to visit localhost:8080. Nothing in the fpm log files. Copying that here just in case: [15-Dec-2017 17:04:03] NOTICE: fpm is running, pid 21 [15-Dec-2017 17:04:03] NOTICE: ready to handle connections [15-Dec-2017 17:04:03] NOTICE: systemd monitor interval set to 10000ms I have searched the entire directory structure of the site and can't see any debug.log file. Where might that reside? Though I think it's just not appearing because it doesn't exist yet. The only thing in the nginx log file is redirects from /www/admin/index.php to /www/admin/install.php and back again. It appears to be the same as this issue:
  7. I'm getting the 302 error ERR_TOO_MANY_REDIRECTS on my Revive Adserver installation. It sounds similar to this GitHub issue: https://github.com/revive-adserver/revive-adserver/issues/151 curl $domain/www/admin/install.php returns nothing. The issue isn't with my NGINX installation. I'm pasting it below, but the thing is that if I change `index index.php` to `index index.html` and add a simple html file at /var/www/html/index.html then that file serves fine. It seems that for some reason the PHP code has created an infinite redirect loop when `index index.php` calls that file in my build. I have tried clearing my cookies/browser cache/session data and completely starting from scratch with a fresh build without success. Any suggestions on what might be the issue and how I could debug? Thank you for any help! Please let me know if there's any further information I might provide. nginx.conf: ``` user www-data; worker_processes 2; error_log /var/log/nginx/error.log error; pid /var/run/nginx.pid; events { worker_connections 1024; } http { include mime.types; default_type application/octet-stream; sendfile on; keepalive_timeout 65; log_format main '$remote_addr - $remote_user [$time_local] "$request" ' '$status $body_bytes_sent "$http_referer" ' '"$http_user_agent" "$http_x_forwarded_for"'; server { listen 80; server_name localhost; client_max_body_size 4M; client_body_buffer_size 128k; access_log /var/log/nginx/localhost.access.log; error_log /var/log/nginx/localhost.error.log; root /var/www/html; index index.php; location ~ \.php$ { try_files $uri =404; include fastcgi_params; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_pass unix:/var/run/php5-fpm.sock; } } } ```
  8. Hi - I'm new to Revive Adserver, but really appreciate what you all are building. I'd love to get involved. The first thing I'd like to do is help with the API setup and documentation. Is that something that would be desirable? I'm seeing quite a few unanswered questions about it and would love to contribute what I learn as I install it myself. Please bear with me - my first question is where could I contribute PR's to the documentation? I don't see anything on GitHub. In terms of the API, I've done the following and still receive this response when I navigate to http://localhost:8080/www/api/v2/xmlrpc/: ``` <methodResponse> <fault> <value> <struct> <member> <name>faultCode</name> <value> <int>105</int> </value> </member> <member> <name>faultString</name> <value> <string>XML error: Invalid document end at line 1</string> </value> </member> </struct> </value> </fault> </methodResponse> ``` Here's what I did (pasting from my Dockerfile): ``` RUN apt-get install -y php5-fpm RUN apt-get install -y php5-curl RUN apt-get install -y php5-gd RUN apt-get install -y php5-json RUN apt-get install -y php5-mysql RUN apt-get install -y php-pear RUN apt-get install -y curl RUN pear install XML_RPC2 ``` I built the Revive server, created an advertiser, banner, zone, website all manually. No problems at all doing that. Then I went into the InvocationTags plugin and enabled the "Allow XML-RPC Invocation Tag" setting. After doing the above, I still get that error when I try to navigate to that endpoint. Is there a next step to beginning to access the API? Thank you for any help!
×
×
  • Create New...