Can't login to console!

[sjauld]

Issue

Short description

Brief description of what happened

I have an Ant Media Server cluster with a MongoDB backend that was working nicely on v1.6.1. After upgrading to v1.7.2, I can't log in anymore (403 error).

Environment

• Operating system and version: AMS Enterprise v1.7.2 AMI
• Java version: AMS Enterprise v1.7.2 AMI
• Ant Media Server version: AMS Enterprise v1.7.2 AMI
• Browser name and version: AMS Enterprise v1.7.2 AMI

Expected behavior

Put as much detail here as possible
I can log in

Actual behavior

Put as much detail here as possible
I can't log in

Steps to reproduce

1. Deploy a working cluster using AMS v1.6.1 with a MongoDB backend
2. Set an admin password
3. Upgrade the cluster to v1.7.2
4. Try to log in

Logs

Place logs on pastebin or elsewhere and put links here

Join Google Group and be a part of Ant Media Server Community.

[mekya]

Are you sure you set the correct parameters for MongoDB access while running change_server_mode.sh? Regards, A. Oguz

…

On Thu, Jun 20, 2019 at 8:09 AM Stuart Auld ***@***.***> wrote: Issue Short description *Brief description of what happened* I have an Ant Media Server cluster with a MongoDB backend that was working nicely on v1.6.1. After upgrading to v1.7.2, I can't log in anymore (403 error). Environment - Operating system and version: AMS Enterprise v1.7.2 AMI - Java version: AMS Enterprise v1.7.2 AMI - Ant Media Server version: AMS Enterprise v1.7.2 AMI - Browser name and version: AMS Enterprise v1.7.2 AMI Expected behavior *Put as much detail here as possible* I can log in Actual behavior *Put as much detail here as possible* I can't log in Steps to reproduce 1. Deploy a working cluster using AMS v1.6.1 with a MongoDB backend 2. Set an admin password 3. Upgrade the cluster to v1.7.2 4. Try to log in Logs *Place logs on pastebin <http://pastebin.com/> or elsewhere and put links here* Join Google Group <https://groups.google.com/forum/#!forum/ant-media-server> and be a part of Ant Media Server Community. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1336?email_source=notifications&email_token=AA2LZ6Y42JCK46BUFRKWT6LP3MGIFA5CNFSM4HZPMOHKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G2R3FZQ>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA2LZ6YFJP3IGAFW44JBS33P3MGIFANCNFSM4HZPMOHA> .

[sjauld]

Hi @mekya,

Yes, we haven't changed this, we're running all of the same userdata, just on the new AMI.

Cheers,
Stuart

[mekya]

Is it possible to send me log file of the server you're trying to login? I can check what's wrong with it. Thank you

…

On Thu, Jun 20, 2019 at 9:07 AM Stuart Auld ***@***.***> wrote: Hi @mekya, Yes, we haven't changed this, we're running all of the same userdata, just on the new AMI. Cheers, Stuart — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[sjauld]

I'll sent them via email now!

[mekya]

Thank you. I'm just letting the same answer be here as well. It seems that this issue is about Chrome caching or something. There is no special error for this in logs. Could you please try to login with firefox? If you could succeed to login with firefox, I'll create an issue about what's wrong with Chrome. Thank you Regards, A. Oguz

…

On Fri, Jun 21, 2019 at 2:09 AM Stuart Auld ***@***.***> wrote: I'll sent them via email now! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1336?email_source=notifications&email_token=AA2LZ63QP77CTTJLAM7STJLP3QEZPA5CNFSM4HZPMOHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYG7GHI#issuecomment-504230685>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA2LZ6Y5WPAW3NWK2GY52JTP3QEZPANCNFSM4HZPMOHA> .

[sjauld]

Hi Oguz, I have tried in Safari and also in Chrome (private mode) but still getting 403 errors - I don't think it's a caching issue. Cheers, Stuart On Fri, 21 Jun 2019 at 17:43, Ahmet Oğuz Mermerkaya < notifications@github.com> wrote:

…

Thank you. I'm just letting the same answer be here as well. It seems that this issue is about Chrome caching or something. There is no special error for this in logs. Could you please try to login with firefox? If you could succeed to login with firefox, I'll create an issue about what's wrong with Chrome. Thank you Regards, A. Oguz On Fri, Jun 21, 2019 at 2:09 AM Stuart Auld ***@***.***> wrote: > I'll sent them via email now! > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > < #1336?email_source=notifications&email_token=AA2LZ63QP77CTTJLAM7STJLP3QEZPA5CNFSM4HZPMOHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYG7GHI#issuecomment-504230685 >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AA2LZ6Y5WPAW3NWK2GY52JTP3QEZPANCNFSM4HZPMOHA > > . > — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1336?email_source=notifications&email_token=AB6Z4NZGWTFQHOAC24SHBW3P3SBCXA5CNFSM4HZPMOHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYHWYTQ#issuecomment-504327246>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB6Z4N6XU5I23SWVZS3PA43P3SBCXANCNFSM4HZPMOHA> .

[mekya]

Can you provide me to access your server temporarily and check what's going on? ssh and web panel credentials. Regards, A. Oguz On Mon, Jun 24, 2019 at 2:39 AM Stuart Auld <notifications@github.com> wrote:

…

Hi Oguz, I have tried in Safari and also in Chrome (private mode) but still getting 403 errors - I don't think it's a caching issue. Cheers, Stuart On Fri, 21 Jun 2019 at 17:43, Ahmet Oğuz Mermerkaya < ***@***.***> wrote: > Thank you. I'm just letting the same answer be here as well. > > > It seems that this issue is about Chrome caching or something. There is no > special error for this in logs. > Could you please try to login with firefox? > > If you could succeed to login with firefox, I'll create an issue about > what's wrong with Chrome. > > Thank you > Regards, > A. Oguz > > On Fri, Jun 21, 2019 at 2:09 AM Stuart Auld ***@***.***> > wrote: > > > I'll sent them via email now! > > > > — > > You are receiving this because you were mentioned. > > Reply to this email directly, view it on GitHub > > < > #1336?email_source=notifications&email_token=AA2LZ63QP77CTTJLAM7STJLP3QEZPA5CNFSM4HZPMOHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYG7GHI#issuecomment-504230685 > >, > > or mute the thread > > < > https://github.com/notifications/unsubscribe-auth/AA2LZ6Y5WPAW3NWK2GY52JTP3QEZPANCNFSM4HZPMOHA > > > > . > > > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > < #1336?email_source=notifications&email_token=AB6Z4NZGWTFQHOAC24SHBW3P3SBCXA5CNFSM4HZPMOHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYHWYTQ#issuecomment-504327246 >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AB6Z4N6XU5I23SWVZS3PA43P3SBCXANCNFSM4HZPMOHA > > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1336?email_source=notifications&email_token=AA2LZ6Y5IQ2GLR3DHTEVEFLP4ACSDA5CNFSM4HZPMOHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYLJWFY#issuecomment-504797975>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA2LZ664YLZIWVZNYDBPKYTP4ACSDANCNFSM4HZPMOHA> .

[mekya]

This issues for CORS related and it's fixed in 1.8.0

In order to make it work for https in 1.7.2, you should open the file /usr/local/antmedia/webapps/root/WEB-INF/web.xml
and replace the lines below

<filter>
        <filter-name>CorsFilter</filter-name>
        <filter-class>org.apache.catalina.filters.CorsFilter</filter-class>
        <init-param>
          <param-name>cors.allowed.origins</param-name>
          <param-value>http://localhost:4200</param-value>
        </init-param>
        <init-param>
          <param-name>cors.support.credentials</param-name>
          <param-value>true</param-value>
        </init-param>
    </filter>

with these ones

<filter>
        <filter-name>CorsFilter</filter-name>
        <filter-class>org.apache.catalina.filters.CorsFilter</filter-class>
        <init-param>
          <param-name>cors.allowed.origins</param-name>
          <param-value>*</param-value>
        </init-param>
    </filter>

restart the servers