-
Notifications
You must be signed in to change notification settings - Fork 2
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
Network Error and AxiosError 403 When getting Transactions #265
Comments
Thank you for sharing all these details. This helped a lot to identify a recommended next step, and hopefully a solution for you. I noticed that you added some custom port mapping to the YAFFA web application uses Laravel framework and several features and components of the framework. In order to adapt the behavior of the application to the changed ports, you need to add the
Without this setting, many API calls fail, making the UI empty, or unresponsive. Using your Some related discussions mention that the Please let me know if this helps you to proceed further. |
Hi, thank you for your reply. Unfortunately, it did not work for me. I looked into the Another notification that I noticed is that Microsoft Edge tells me that the instance is not fully secure. Exact message:
I checked the network calls made by the website on a reload and saw that for favicon.ico, an HTTP request is made at Do you have any suggestions on what I can look into next? If it is all right, can I contribute to the documentation with the instructions for a docker installation later after this gets figured out? |
@acciptris , could you please share your updated .env file, so I can check further? On my end (using Windows/WSL2 as a host) I was able to get the app fully functional using your original docker-compose.yml and .env files. This latter was updated only with the app key and the Sanctum domain settings. Yes, I'd be happy to add any extension to the documentation and installation instructions, including changes from contributors. |
.env:
docker-compose.yaml:
Hi. Here are the modified config files. The thing I said about the HTTP request made, was there even before the modification. I am trying this on a Digitalocean Droplet VPS. Did you face anything similar when you hosted the demo website for YAFFA? |
Quick question @acciptris , just to avoid any misdirection on my end. Are you using exactly these values in your .env file, or have you replaced your actual domain and subdomain settings before posing the file content? SANCTUM_STATEFUL_DOMAINS=subdomain.domain.com |
@kantorge I have replaced my URL with placeholder values here. I did verify that I am using the correct values in my actual env file. |
Thanks for confirming @acciptris , that's absolutely reasonable. I ended up creating a VM in GCP with Docker and Docker Compose, using your .env and YAML files, and also setting creating a DNS record for a test subdomain pointing to the IP of this VM. The key setting I had to make is to add the necessary ports to the Sanctum settings: This allowed me to spin up and use YAFFA. Note, that given your settings of the volumes, I also had to adjust the folder permissions within Docker:
Let me know if this helps you to get started. I'm planning to create a step-by-step guide of this approach in the documentation. Any notes and contributions are welcome. |
Hi,
Thank you for creating this project.
I am trying to setup yaffa on a VPS through docker container. I was able to install it, but I am not able to add a transaction because accounts are not showing up even though I have added an account. Also some buttons on the UI are not responsive. On the dashboard, I am getting an error saying "There was an error while getting account data: Network Error".
On the transactions page, I get this error which has a little more information: "Error getting transactions: AxiosError: Request failed with status code 403".
Following are the configurations file that I am using:
docker-compose.yaml
.env
I would appreciate any suggestions on how to resolve this error. I suspect this issue is due to connection error between the docker containers running the app and the db, but I am not sure about it. I am happy to share more information if needed.
Thanks
The text was updated successfully, but these errors were encountered: