[GH-ISSUE #577] Paymenter don't work #13588

New Issue

GiteaMirror · 2026-06-17T05:49:21-05:00

GiteaMirror commented

2026-06-17 05:49:21 -05:00

Originally created by @neyunse on GitHub (Dec 9, 2025).
Original GitHub issue: https://github.com/Dokploy/templates/issues/577

Template Name

Paymenter

Relevant Logs of the Error

No relevant errors appear in the Dokploy logs; only when accessing the page does it remain blank.
When accessing the console, it can be seen that the problem is “Cross-origin request blocked: The same-origin policy does not allow reading remote resources at http://localhost/default/assets/app-DKCq4tKC.js. (Reason: CORS request unsuccessful). Status code: (null)”.

Steps to Reproduce the Error

Deploy the Paymenter template
Access to the web domain
The page not load.

Environment Information

OS: Ubuntu 20
Dokploy: 0.25.11
VPS Provider: No (Self hosted)

When does this error occur?

When accessing the application

Additional Context

It seems that there is a problem with APP_URL. When configuring the URL, it continues to use http://localhost/*. This is causing resources to fail to load.

In simple tests, I saw that APP_URL reaches the container, but for some reason it is not being modified in the template.

Will you send a PR to fix it?

No

Originally created by @neyunse on GitHub (Dec 9, 2025). Original GitHub issue: https://github.com/Dokploy/templates/issues/577 ### Template Name Paymenter ### Relevant Logs of the Error No relevant errors appear in the Dokploy logs; only when accessing the page does it remain blank. When accessing the console, it can be seen that the problem is `“Cross-origin request blocked: The same-origin policy does not allow reading remote resources at http://localhost/default/assets/app-DKCq4tKC.js. (Reason: CORS request unsuccessful). Status code: (null)”.` ### Steps to Reproduce the Error 1. Deploy the Paymenter template 2. Access to the web domain 3. The page not load. ### Environment Information ```bash OS: Ubuntu 20 Dokploy: 0.25.11 VPS Provider: No (Self hosted) ``` ### When does this error occur? When accessing the application ### Additional Context It seems that there is a problem with APP_URL. When configuring the URL, it continues to use http://localhost/*. This is causing resources to fail to load. In simple tests, I saw that APP_URL reaches the container, but for some reason it is not being modified in the template. ### Will you send a PR to fix it? No

GiteaMirror added the bug label 2026-06-17 05:49:21 -05:00

GiteaMirror closed this issue

2026-06-17 05:49:22 -05:00

GiteaMirror commented

2026-06-17 05:49:23 -05:00

@neyunse commented on GitHub (Dec 10, 2025):

OK! I see how! For anyone else with the same problem...
(and this only works if you use Dokploy self-host and have access to your server's terminal)

remove database service. (Since it will be more convenient to create a separate custom database.)
Create a database; I used mariadb.
Edit the compose by adding the following environments: DB_CONNECTION=mariadb, DB_URL=${DB_URL}, DB_HOST=${DB_HOST}, DB_PORT=${DB_PORT}, DB_DATABASE=${DB_DATABASE}, DB_USERNAME=${DB_USERNAME}, DB_PASSWORD=${DB_PASSWORD}
Configure your environments with your database settings.
Wait for your independent database to initialize correctly.
Click on “Deploy.” and wait
Go to domains and set up a domain by choosing the “Paymenter” service. (It is important that you also configure it in APP_URL)
Go to the terminal and connect to the server with ssh.
Check the container name with docker ps
run: docker exec -it <container name> sh -c "php artisan app:init" (Fill in the information. In the URL input field, enter the domain you configured.)
run: docker exec -it <container name> sh -c "php artisan db:seed --class=CustomPropertySeeder" (Choose “yes”)
run: docker exec -it <container name> sh -c "php artisan app:user:create" (Create a user as Admin)
Stop the application from dockploy and redeploy it (this is not necessary if the URL loads correctly when entering the domain; I did it just in case).

And that's it, the app should now be running on the domain.

@neyunse commented on GitHub (Dec 10, 2025): OK! I see how! For anyone else with the same problem... (and this only works if you use Dokploy self-host and have access to your server's terminal) 1. remove database service. (Since it will be more convenient to create a separate custom database.) 2. Create a database; I used mariadb. 3. Edit the compose by adding the following environments: DB_CONNECTION=mariadb, DB_URL=${DB_URL}, DB_HOST=${DB_HOST}, DB_PORT=${DB_PORT}, DB_DATABASE=${DB_DATABASE}, DB_USERNAME=${DB_USERNAME}, DB_PASSWORD=${DB_PASSWORD} 4. Configure your environments with your database settings. 5. Wait for your independent database to initialize correctly. 6. Click on “Deploy.” and wait 7. Go to domains and set up a domain by choosing the “Paymenter” service. (It is important that you also configure it in APP_URL) 8. Go to the terminal and connect to the server with ssh. 9. Check the container name with `docker ps` 10. run: `docker exec -it <container name> sh -c "php artisan app:init"` (Fill in the information. In the URL input field, enter the domain you configured.) 11. run: `docker exec -it <container name> sh -c "php artisan db:seed --class=CustomPropertySeeder"` (Choose “yes”) 12. run: `docker exec -it <container name> sh -c "php artisan app:user:create"` (Create a user as Admin) 13. Stop the application from dockploy and redeploy it (this is not necessary if the URL loads correctly when entering the domain; I did it just in case). And that's it, the app should now be running on the domain.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/templates#13588