search

awslabs / web-client-for-aws-transfer-family

This solution creates a web portal for your customers to access your corporate Secure Shell File Transfer Protocol (SFTP) environment. It combines the benefits of using AWS Transfer for SFTP with an intuitive web browser interface for your non-technical users.
https://aws.amazon.com/solutions/implementations/web-client-for-aws-transfer-family/?did=sl_card&trk=sl_card
Apache License 2.0
73 stars 41 forks source link

Cannot login, blank red box, page shows JS errors & not able to authenticate #14

Open sapra5379 opened 2 years ago

sapra5379 commented 2 years ago

Hello Team, Looking for the support to review my setup, as i am getting red error without message in web UI and need to understand authentication and directory mapping on DynamoDB.

sapra5379 commented 2 years ago

error

sapra5379 commented 2 years ago

DynamoDb 3

sapra5379 commented 2 years ago

@amazon-auto please help into it.

electrokat commented 2 years ago

@shardhak this is the same issue that I'm experiencing.

@sapra5379 can you screenshot the browser logs on Chrome (redact your SFTP URL) by pressing F12 (Developer mode) on the webpage after you login?

Raydingo commented 1 year ago

Hello. was anyone able to solve this? I'm running in to the same issue.

kshardha commented 1 year ago

Can you share the error from dev console logs?

Raydingo commented 1 year ago

Can you share the error from dev console logs?

Hi kshardha, here is the screenshot.

image

kshardha commented 1 year ago

Check your Flask configuration file (backend) and the entries you had for your domain etc in 04a script. Also, check if the certs you are using allow for the FQDN you are configuring for the application.

Raydingo commented 1 year ago

Check your Flask configuration file (backend) and the entries you had for your domain etc in 04a script. Also, check if the certs you are using allow for the FQDN you are configuring for the application.

The flash configuration file and the 04a script contain the same domain/cname configuration. I am using a wildcard cert. *domainname.com

kshardha commented 1 year ago

One more thing to check, share the ECS logs for the backend tasks that are running. See if you have encountered any error there.

Raydingo commented 1 year ago

ECS_LOG.xlsx

log attached.

kshardha commented 1 year ago

Try updating the requirement.txt file using the following and rebuild docker image, upload it and re-create the ECS tasks:

Werkzeug==2.0.0 jinja2==3.0.3 Flask==2.1.0 Flask-Cors==3.0.8 Paramiko==2.7.1 flask_jwt_extended==3.25.1 gunicorn==20.0.4 boto3==1.14.24 cachetools==4.1.1 requests==2.24.0 psutil==5.7.2

RiteshC05 commented 1 year ago

Is there any solution to this bug? Currently facing the same issue. In the console window, the error message starts with "Unexpected token '<', \"<!DOCTYPE..>" Is there a problem with the response returning an html file?