Search results

Hello, @Martin73 You can use one of this methods (or all of them) to improve your server protection Enable fail2ban in Tools & Settings > IP Address Banning It will automatically ban suspicious IPs by system firewall rules Try to enable Tools & Settings > Web Application Firewall...

Nginx and apache have different configs. If nginx enabled as a reverse proxy it handle request first. Process custom rules, adds cookies, etc. Then pass this request to apache and return answer from apache to end user. Some requests can be handled by nginx and not passing to apache (for example...

Check webserver access log to ensure request handler properly. Also try to add some debug logging to your routing script. Write all requests and it's params to a file. Use log to verify routing logic.

You need to add the A record to domain DNS pointing to your IP address. Then choose in domain > Hosting Settings > Preferred domain with www. You can not issue a certificate for www subdomain only.

All configs are result of processing templates each time domain configuration updated. You need to change templates instead of configs - look at /usr/local/psa/admin/conf/templates/default/domain/domainVirtualHost.php

There are lots of different settings and options in your post. I suppose it's hard to find a root cause of your problem in such complicated situation. Try to create a test domain and with default options and add settings one by one, check result after each change. This way you can find how...

Change index.php to your front controller (or a page that can route urls)

Hello @DieterWerner Go to Domain > Apache & nginx Settings Disable Nginx Proxy mode And add this directive to the Additional nginx directives section location = / { index index.php; try_files $uri $uri/ /index.php$is_args$args; } This will send all requests for non existent files...

Correct You do not need pass 'base_domain' option if you would like create a new subscription. PS Did you tried CLI endpoint from my previous posting?

Try set env without equal sign like this --env JENKINS_OPTS="--prefix /jenkins"

When you use /domains endpoint in REST it creates a subscription when no 'base_domain' nor 'parent_domain' provided. You can use all CLI commands using /cli endpoint like this POST https://{{api_host}}:{{api_port}}/api/v2/cli/subscription/call Accept: application/json X-API-Key: {{api_token}}...

Hope this will helps

Example of creating a domain using REST API POST https://{{api_host}}:{{api_port}}/api/v2/domains Accept: application/json X-API-Key: {{api_token}} { "name": "test.dev", "hosting_type": "virtual", "hosting_settings": { "ftp_login": "test_login", "ftp_password": "test_password"...

Hello, most recent documentation incl. swagger scheme and playground can be found under Tools & Settings > Server Management > Remote API (REST) page.

Did you try to setup certificate for IP using Tools & Settings > IP Addresses > IP Address edit page? Also, you could set mentioned domain as default for that dedicated IP using same edit page. Please, let know is this helps.

@Santi i'm glad you have solved your problem Regarding proxy_redirect option, it's not work as you expect It just used to modify redirecting inside domain. BTW seems proxy_pass https://127.0.0.1:32771; is a right solution. PS Try this image sameersbn/docker-gitlab if you have enough time...

Thanks for a good explanation, @Santi Let's look in details: When you open this URL: - Client resolve DNS record for gitlab.mydomain.com (which is pointed to your host public IP) - Then send request (open socket connection) to port 32771. In this particular case front-end nginx (listening on...

Can you open Domains > Your domain > Hosting Settings and check that SSL/TLS support checkbox is enabled under Security section?

Hello, you need to follow this steps: - Create subdomain gitlab.mydomain.com - Add custom rule for gitlab.mydomain.com nginx (or apache, if nginx is not installed) to proxy requests to docker container location / { proxy_pass http://127.0.0.1:[gitlab docker port]...

Hello, IP Address can be secured only using self-signed certificate (will be show browser warning about invalid or insecure certificate, but you can ignore this for sure). But better solution is delegate a domain to this IP and issue LetsEncrypt certificate which will be valid for all browsers...