Jump to content

mabass

Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by mabass

  1. How can I sign up for a VPS with a non-american address? Ordering with paypal or credit card fails otherwise.
  2. That's fantastic news. Are you set financially? I'd happily contribute to a donation drive. If only to see it go beyond 17.000$ as final salute to cpanel.
  3. Ah perfect, I wasn't sure if that would only disable my personal view or the entire logging process. Thanks.
  4. Hi, as per title: Is this possible? Rather than dealing with DSGVO-Hassle (which would be required, as IPs are considered personal data) I'd rather just disable it and be done with it.
  5. Thanks I'll def. look into that. For now this topic can be closed I think.
  6. No sorry, I was unclear. I added a new subdomain audax-abc.mabass.heliohost.org, with /audax-abc/ as root. Basically the same app is now running twice, once via the sandbox (accessed by mabass.tk) and as standalone (audax-abc). I just wanted to use the standalone the same httpd conf method.
  7. Happy to help, DENIC stopped complaining as well. My issue's also resolved, the routing now works as intended. Topic can be closed.
  8. True. Very odd. Could you do me a favor and do the same for public_html/audax-abc ? I mirrored the specific app in it's own folder. That way I can provide a stable version while still testing. Anyway, thanks for all your help. For now I've run out of ideas, maybe stackoverflow has an idea. Edit: One thing I have not tried is profiling the app using werkzeug. However, do that I need to wrap the wsgi app and I'm not sure how to do that with your infrastructure. A basic example to deploy the profiler is provided here (under section "Profiling for Perfomance") - however the example code uses now deprecated imports.
  9. Doing more testing, and it def. seems to be tied to server load. Right now Tommy's at 14.14 load (Edit: now at 68) and the form's break reliably, with response times around 1s. I tried pre-loading some image files to cache them user-side but that doesn't seem to help, the response delay is still too high. Have you tried switchting to the httpd.conf method? I don't know enough about Apache/wsgi to tell if this could result in a speed gain. Edit: More testing. I'm observing a correlation with htaccess and related domains. If I reduce my ht-access to the bare minium, the waiting delays seem to improve.
  10. Thanks, though I think I fixed that specific issue shortly after. I'll have a closer look tomorrow. Anyway, thanks for taking your time. This is amazing support.
  11. UDP Port 53 according to their docs.
  12. Hm, I still get the issue occassionally; in any case I had switched %1 to %{Request... some time after I had first noticed the issue. It's more pronounced on the other form - any "first" time the form is submitted, the delay hits ~1s; the second submit it works fine and the download link is displayed. My best guess is that somehow my app causes a longer waiting-delay on heliohost than it does on e.g. pythonanywhere and flask's routing breaks as a result. Maybe it's related to accessing (and in the case of the form linked above: writing) files? That said, the issue seemed to be worse a few hours ago when Tommy's load was around ~10; now it's around ~5. That's anecdotal however.
  13. Did a bit more testing with networking tools and the problem more often than not corresponds with longish server delays. The initial (failing) POST-request has nearly one full second waiting delay. After running the app successfully once, the waiting's down to ~150-200ms. Whenever, for whatever reason, the delay jumps above 500ms the app seems to break as described. Not sure if there's much to be done about it besides switching to a VPS?
  14. Alright thanks. It's indeed a recent change. I was confused as it was properly refering to heliohost but ending up in the root public_html. Should I be concerned that DENIC is complaining about being unable to access a port?
  15. I'd assume the former, as I can't find any .htaccess files (though py-anywhere is more restrictive in what I can access, so they might be forcibly hidden). And sure, I'd give that a shot. Here's pyanywhere's full wsgi for completeness sake - not much different tbh. # This file contains the WSGI configuration required to serve up your # web application at http://<your-username>.pythonanywhere.com/ # It works by setting the variable 'application' to a WSGI handler of some # description. # # The below has been auto-generated for your Flask project import sys # add your project directory to the sys.path project_home = '/home/Wolfenswan/sandbox' if project_home not in sys.path: sys.path = [project_home] + sys.path # import flask app but need to call it "application" for WSGI to work from app import app as application # noqa
  16. Hi, I'm trying to configure the addon-domain audax-abc.de but am running into issues. The new subdomain audax-abc.mabass.heliohost.org works as intended, with custom htaccess routing. However, audax-abc.de ends up refering to mabass.heliohost.org, instead of behaving as expected. This might possibly be related to the .de-woes described here and here The DENIC predelegation check does indeed complain when testing audax-abc.de Though maybe I've missed something?
  17. That's def. true I'm just stumped what could be causing this. Why would the script accept the POST without issues the first time but refuse the redirect, but then work almost all times afterwards - until the next forced reload of the page? And that only on heliohost, not on pythonanywhere(which also uses wsgi). So weird.
  18. Using action="" is generally the recommended way with Flask (and wtfforms), as the POST-request is then handled by the flask-routes, using redirect(). Also, the issue persists on pages with only one form. The barebones examples works the exact same way as well, using action="" @app.route('/form-1', methods=["GET", "POST"]) def index(i='None yet'): flash(f'1 Request:{request.method}') if request.method == "POST": flash(f'2 Input: {request.form.get("input")}') i = request.form.get("input") return redirect(url_for('.success',i=i)) return render_template('form-vanilla.html',i=i) @app.route('/form-2', methods=["GET", "POST"]) def form_2(i='None yet'): form = InputForm() flash(f'1 Request:{request.method}') if form.validate_on_submit(): flash(f'2 Input: {form.word.data}') i = form.word.data return redirect(url_for('.success',i=i)) return render_template('form-wtf.html',i=i,form=form) @app.route('/success', methods=["GET"]) def success(): i = request.args.get('i') return render_template('index.html',i=i) I have a hunch that the issue might lie in the re-routing through flask.wsgi, as that's the only concernable difference between localhost, pythonanywhere und heliohost. I'll try and see if changing action="" helps, but it might be tricky to realize.
  19. Hi, I'm running into an odd issue with two of my flask-based web-apps providing user-input forms. EDIT: Ignore the "writing files" part in the title - more testing shows it's not related to this aspect. The issue: After submitting the form the page seems to accept the POST-request without hiccup, no error messages are displayed. However, none of the intended functionality actually takes place, the page containing the form simply reloads instead of properly redirecting. However, if attempting to submit a second time, everything works perfectly fine (*most of the time: sometimes it takes a third attempt). After it worked once, forms will behave as expected. Reloading the page manually, i.e. resetting the form, causes the error to appear again. This issue does not occur on localhost or on pythonanywhere. Testing: If you want to test it for yourselves it's done the easiest with https://mabass.tk/adx_abctrainer/ Enter anything in the first field and press the button next to it OR simply press the "Los!" button below. Expected behavior: Redirect to page showing images corresponding to the entered word, e.g. https://mabass.tk/adx_abctrainer/heliohost Actual Result: No response on first submit, page reloads. The fact that errors are displayed for the second form below but not the first one is prove that the POST-request is registered. The usage of two forms on one page isn't the issue here. This page is simply the easiest to reproduce the issue with. For comparison, here's the identical app on pythonanywhere, working as intended: http://wolfenswan.pythonanywhere.com/adx_abctrainer/ More testing: I deployed a super simple flask app with two forms, one using wtfforms, the other pure html. Irritatingly, these two seem to work just fine.
  20. Thanks! With some more tinkering I got it to work as intended. Just leaving my ht-access here, in case people google a similar issue and are looking for pointers: RewriteCond %{HTTP_HOST} ^mabass\.heliohost\.org$ [NC] RewriteRule ^(.*)$ flask-live/flask.wsgi/$1 [QSA,PT,L] RewriteCond %{HTTP_HOST} ^mabass\.tk$ [NC,OR] RewriteCond %{HTTP_HOST} ^mabass\.de$ [NC] RewriteRule ^(.*)$ flask.wsgi/$1 [QSA,PT,L]
  21. That works, thanks. Just so I get this right: My problem wasn't with the condition but that the subdomain was trying to route through a directory it couldn't find? And if, theoretically, I wanted it to work both with https://mabass.heliohost.org/flask-dev/ (which is now broken) and the subdomain I'd have to split the current RewriteRule into two more specific ones, one catering for each?
  22. Not sure why, but I struggle at grasping mod_rewrite. I understand the general syntax and regex well enough, but the overall logic or structure eludes me. More precisely: I mirrored my flask-instance to into a dev- and live-/production-instance. Both work fine when accessing them from mabass.heliohost.org. However, the sub-domains I created for testing purposes all produce a 500: flask-dev.mabass.heliohost.org - to /flask-dev/ tk.mabass.heliohost.org (for the mabass.tk addon domain) - to /flask-live/ As I understand it, I have to add a RewriteCond to .htaccess, so I added RewriteCond %{HTTP_HOST} ^flask-dev\.mabass\.heliohost\.org$ [NC] producing: RewriteEngine On RewriteBase / RewriteRule ^(media/.*)$ - [L] RewriteRule ^(admin_media/.*)$ - [L] RewriteRule ^(flask\.wsgi/.*)$ - [L] RewriteRule ^(.*)$ flask-dev/flask.wsgi/$1 [QSA,PT,L] RewriteCond %{HTTP_HOST} ^flask-dev\.mabass\.heliohost\.org$ [NC] RewriteRule ^(flask\.wsgi/.*)$ - [L] RewriteRule ^(.*)$ flask-dev/flask.wsgi/$1 [QSA,PT,L] Still, no luck.
  23. I figured, thanks. Another question if you don't mind: I tried adding an addon domain that directly points towards public_html/mabass.tk/ (identical with /flask/ for now), however, this now produces a 500 error due to (I assume) an issue in either the .htaccess or .wsgi. Any pointers what I need to look at? https://mabass.heliohost.org/mabass.tk/ works fine.
  24. Thanks, that helped a lot. After resolving a few more pathing issues everything seems to work as intended now Regarding git/version-control: Is it correct that I can only pull from an existing repository but neither commit/drop local changes? I couldn't find a command line access or the relevant backend-controls in cpanel
×
×
  • Create New...